DNS response history for ns2.web500k.com

ns2.web500k.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 34 DNS check records, 34 successful responses, 0 failed responses, and 543 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.web500k.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

543 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.52.147.83

Most recently resolved hosting IP on selected date

Successful Responses

34

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.web500k.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
34 2026-08-25 12:05 639232556111768563
333 ms 103.52.147.83
33 2026-08-25 11:48 639232545839529039
2007 ms 103.52.147.83
32 2026-08-25 11:31 639232535349285207
836 ms 103.52.147.83
31 2026-08-25 11:13 639232524938080723
343 ms 103.52.147.83
30 2026-08-25 10:19 639232492740373468
334 ms 103.52.147.83
29 2026-08-25 10:02 639232482235303141
336 ms 103.52.147.83
28 2026-08-25 09:45 639232471861770303
338 ms 103.52.147.83
27 2026-08-25 09:27 639232461630217327
327 ms 103.52.147.83
26 2026-08-25 09:10 639232451282965990
344 ms 103.52.147.83
25 2026-08-25 08:53 639232440814614938
334 ms 103.52.147.83
24 2026-08-25 08:36 639232430410720425
2179 ms 103.52.147.83
23 2026-08-25 08:18 639232420003096185
327 ms 103.52.147.83
22 2026-08-25 08:01 639232409467287444
334 ms 103.52.147.83
21 2026-08-25 07:43 639232399077195997
336 ms 103.52.147.83
20 2026-08-25 07:26 639232388731528337
4 ms 103.52.147.83
19 2026-08-25 07:09 639232378288598612
6 ms 103.52.147.83
18 2026-08-25 06:15 639232346196373643
4 ms 103.52.147.83
17 2026-08-25 05:58 639232336112370741
381 ms 103.52.147.83
16 2026-08-25 05:42 639232326146508970
4327 ms 103.52.147.83
15 2026-08-25 05:25 639232316189381720
3 ms 103.52.147.83
14 2026-08-25 05:08 639232306217998913
3 ms 103.52.147.83
13 2026-08-25 04:52 639232296255744174
331 ms 103.52.147.83
12 2026-08-25 04:35 639232286095760789
327 ms 103.52.147.83
11 2026-08-25 04:18 639232276086186273
331 ms 103.52.147.83
10 2026-08-25 04:01 639232265900986425
333 ms 103.52.147.83
9 2026-08-25 03:44 639232255723518075
172 ms 103.52.147.83
8 2026-08-25 03:27 639232245484452890
334 ms 103.52.147.83
7 2026-08-25 03:10 639232235157175331
339 ms 103.52.147.83
6 2026-08-25 02:17 639232203197189095
2176 ms 103.52.147.83
5 2026-08-25 02:00 639232192844564298
3 ms 103.52.147.83
4 2026-08-25 01:42 639232182496008942
339 ms 103.52.147.83
3 2026-08-25 01:25 639232172197053132
338 ms 103.52.147.83
2 2026-08-25 00:32 639232140250307418
3 ms 103.52.147.83
1 2026-08-25 00:15 639232129927860324
4 ms 103.52.147.83