DNS response history for ns2.adeep.su

ns2.adeep.su 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 532 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.adeep.su.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

532 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

193.107.112.60

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.adeep.su

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:06 639231693747052549
129 ms 193.107.112.60
28 2026-08-24 11:49 639231683712487276
2163 ms 193.107.112.60
27 2026-08-24 11:32 639231673513573868
302 ms 193.107.112.60
26 2026-08-24 10:39 639231641791249939
26 ms 193.107.112.60
25 2026-08-24 10:22 639231631866211033
91 ms 193.107.112.60
24 2026-08-24 10:06 639231621644955316
19 ms 193.107.112.60
23 2026-08-24 09:48 639231611478799259
63 ms 193.107.112.60
22 2026-08-24 08:56 639231579923718211
1573 ms 193.107.112.60
21 2026-08-24 08:39 639231569810702936
19 ms 193.107.112.60
20 2026-08-24 08:22 639231559762411619
40 ms 193.107.112.60
19 2026-08-24 08:05 639231549663595407
21 ms 193.107.112.60
18 2026-08-24 07:13 639231518076817246
1706 ms 193.107.112.60
17 2026-08-24 06:56 639231508078650885
21 ms 193.107.112.60
16 2026-08-24 06:40 639231498210697093
146 ms 193.107.112.60
15 2026-08-24 06:23 639231488109699360
114 ms 193.107.112.60
14 2026-08-24 05:31 639231456772510692
19 ms 193.107.112.60
13 2026-08-24 05:14 639231447084631185
53 ms 193.107.112.60
12 2026-08-24 04:58 639231437208519473
62 ms 193.107.112.60
11 2026-08-24 04:41 639231427209627490
48 ms 193.107.112.60
10 2026-08-24 03:49 639231395791246644
1579 ms 193.107.112.60
9 2026-08-24 03:33 639231386075551458
2033 ms 193.107.112.60
8 2026-08-24 03:16 639231376208713791
2034 ms 193.107.112.60
7 2026-08-24 03:00 639231366170589276
20 ms 193.107.112.60
6 2026-08-24 02:07 639231334732159368
47 ms 193.107.112.60
5 2026-08-24 01:51 639231325035670078
31 ms 193.107.112.60
4 2026-08-24 01:35 639231315132253837
2102 ms 193.107.112.60
3 2026-08-24 01:18 639231305014280808
49 ms 193.107.112.60
2 2026-08-24 00:26 639231273779380675
272 ms 193.107.112.60
1 2026-08-24 00:10 639231264180839154
637 ms 193.107.112.60