DNS response history for ns2.prepaidcardgambling.com

ns2.prepaidcardgambling.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 262 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.prepaidcardgambling.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

262 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.233.77.59

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.prepaidcardgambling.com

Showing DNS history for 2026-08-25 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
35 2026-08-25 12:17 639232566381512620
278 ms 173.233.77.59
34 2026-08-25 12:00 639232556111768563
14 ms 173.233.77.59
33 2026-08-25 11:43 639232545839529039
305 ms 173.233.77.59
32 2026-08-25 11:26 639232535349285207
4 ms 173.233.77.59
31 2026-08-25 11:08 639232524938080723
9 ms 173.233.77.59
30 2026-08-25 10:14 639232492740373468
275 ms 173.233.77.59
29 2026-08-25 09:57 639232482235303141
257 ms 173.233.77.59
28 2026-08-25 09:40 639232471861770303
18 ms 173.233.77.59
27 2026-08-25 09:23 639232461630217327
277 ms 173.233.77.59
26 2026-08-25 09:05 639232451282965990
6 ms 173.233.77.59
25 2026-08-25 08:48 639232440814614938
248 ms 173.233.77.59
24 2026-08-25 08:31 639232430410720425
293 ms 173.233.77.59
23 2026-08-25 08:13 639232420003096185
270 ms 173.233.77.59
22 2026-08-25 07:56 639232409467287444
357 ms 173.233.77.59
21 2026-08-25 07:39 639232399077195997
255 ms 173.233.77.59
20 2026-08-25 07:21 639232388731528337
315 ms 173.233.77.59
19 2026-08-25 07:04 639232378288598612
237 ms 173.233.77.59
18 2026-08-25 06:10 639232346196373643
303 ms 173.233.77.59
17 2026-08-25 05:54 639232336112370741
330 ms 173.233.77.59
16 2026-08-25 05:37 639232326146508970
25 ms 173.233.77.59
15 2026-08-25 05:20 639232316189381720
215 ms 173.233.77.59
14 2026-08-25 05:04 639232306217998913
225 ms 173.233.77.59
13 2026-08-25 04:47 639232296255744174
310 ms 173.233.77.59
12 2026-08-25 04:30 639232286095760789
18 ms 173.233.77.59
11 2026-08-25 04:13 639232276086186273
240 ms 173.233.77.59
10 2026-08-25 03:57 639232265900986425
2109 ms 173.233.77.59
9 2026-08-25 03:40 639232255723518075
263 ms 173.233.77.59
8 2026-08-25 03:23 639232245484452890
211 ms 173.233.77.59
7 2026-08-25 03:05 639232235157175331
346 ms 173.233.77.59
6 2026-08-25 02:12 639232203197189095
3 ms 173.233.77.59
5 2026-08-25 01:55 639232192844564298
245 ms 173.233.77.59
4 2026-08-25 01:38 639232182496008942
332 ms 173.233.77.59
3 2026-08-25 01:20 639232172197053132
3 ms 173.233.77.59
2 2026-08-25 00:27 639232140250307418
252 ms 173.233.77.59
1 2026-08-25 00:10 639232129927860324
339 ms 173.233.77.59