DNS response history for ns2.xedge.systems

ns2.xedge.systems 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 29 DNS check records, 29 successful responses, 0 failed responses, and 722 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.xedge.systems.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

722 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

159.69.121.92

Most recently resolved hosting IP on selected date

Successful Responses

29

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.xedge.systems

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
29 2026-08-24 12:07 639231693747052549
3741 ms 159.69.121.92
28 2026-08-24 11:50 639231683712487276
607 ms 159.69.121.92
27 2026-08-24 11:33 639231673513573868
3522 ms 159.69.121.92
26 2026-08-24 10:40 639231641791249939
67 ms 159.69.121.92
25 2026-08-24 10:24 639231631866211033
3826 ms 159.69.121.92
24 2026-08-24 10:07 639231621644955316
1527 ms 159.69.121.92
23 2026-08-24 09:50 639231611478799259
74 ms 159.69.121.92
22 2026-08-24 08:57 639231579923718211
9 ms 159.69.121.92
21 2026-08-24 08:41 639231569810702936
57 ms 159.69.121.92
20 2026-08-24 08:24 639231559762411619
69 ms 159.69.121.92
19 2026-08-24 08:07 639231549663595407
66 ms 159.69.121.92
18 2026-08-24 07:14 639231518076817246
1522 ms 159.69.121.92
17 2026-08-24 06:58 639231508078650885
31 ms 159.69.121.92
16 2026-08-24 06:41 639231498210697093
2083 ms 159.69.121.92
15 2026-08-24 06:25 639231488109699360
1647 ms 159.69.121.92
14 2026-08-24 05:32 639231456772510692
4 ms 159.69.121.92
13 2026-08-24 05:16 639231447084631185
5 ms 159.69.121.92
12 2026-08-24 04:59 639231437208519473
67 ms 159.69.121.92
11 2026-08-24 04:43 639231427209627490
67 ms 159.69.121.92
10 2026-08-24 03:50 639231395791246644
10 ms 159.69.121.92
9 2026-08-24 03:34 639231386075551458
10 ms 159.69.121.92
8 2026-08-24 03:18 639231376208713791
3 ms 159.69.121.92
7 2026-08-24 03:01 639231366170589276
75 ms 159.69.121.92
6 2026-08-24 02:09 639231334732159368
68 ms 159.69.121.92
5 2026-08-24 01:52 639231325035670078
68 ms 159.69.121.92
4 2026-08-24 01:36 639231315132253837
10 ms 159.69.121.92
3 2026-08-24 01:19 639231305014280808
1685 ms 159.69.121.92
2 2026-08-24 00:27 639231273779380675
23 ms 159.69.121.92
1 2026-08-24 00:11 639231264180839154
3 ms 159.69.121.92