DNS response history for ns2.surge.world

ns2.surge.world 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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 284 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.surge.world.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

284 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.38.166.73

Most recently resolved hosting IP on selected date

Successful Responses

28

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.surge.world

Showing DNS history for 2026-08-24 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
28 2026-08-24 11:47 639231683712487276
223 ms 209.38.166.73
27 2026-08-24 11:30 639231673513573868
111 ms 209.38.166.73
26 2026-08-24 10:37 639231641791249939
300 ms 209.38.166.73
25 2026-08-24 10:21 639231631866211033
374 ms 209.38.166.73
24 2026-08-24 10:04 639231621644955316
228 ms 209.38.166.73
23 2026-08-24 09:47 639231611478799259
367 ms 209.38.166.73
22 2026-08-24 08:54 639231579923718211
100 ms 209.38.166.73
21 2026-08-24 08:37 639231569810702936
89 ms 209.38.166.73
20 2026-08-24 08:20 639231559762411619
412 ms 209.38.166.73
19 2026-08-24 08:03 639231549663595407
374 ms 209.38.166.73
18 2026-08-24 07:11 639231518076817246
2379 ms 209.38.166.73
17 2026-08-24 06:55 639231508078650885
263 ms 209.38.166.73
16 2026-08-24 06:38 639231498210697093
427 ms 209.38.166.73
15 2026-08-24 06:21 639231488109699360
100 ms 209.38.166.73
14 2026-08-24 05:29 639231456772510692
96 ms 209.38.166.73
13 2026-08-24 05:13 639231447084631185
66 ms 209.38.166.73
12 2026-08-24 04:56 639231437208519473
100 ms 209.38.166.73
11 2026-08-24 04:40 639231427209627490
270 ms 209.38.166.73
10 2026-08-24 03:47 639231395791246644
286 ms 209.38.166.73
9 2026-08-24 03:31 639231386075551458
310 ms 209.38.166.73
8 2026-08-24 03:15 639231376208713791
113 ms 209.38.166.73
7 2026-08-24 02:58 639231366170589276
84 ms 209.38.166.73
6 2026-08-24 02:06 639231334732159368
12 ms 209.38.166.73
5 2026-08-24 01:49 639231325035670078
268 ms 209.38.166.73
4 2026-08-24 01:33 639231315132253837
146 ms 209.38.166.73
3 2026-08-24 01:16 639231305014280808
279 ms 209.38.166.73
2 2026-08-24 00:24 639231273779380675
91 ms 209.38.166.73
1 2026-08-24 00:08 639231264180839154
94 ms 209.38.166.73