DNS response history for ns2.sydo.net

ns2.sydo.net 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-26. For this date, NameServerHistory found 36 DNS check records, 35 successful responses, 1 failed responses, and 180 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.sydo.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

180 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

79.170.43.3

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.sydo.net

Showing DNS history for 2026-08-26 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
36 2026-08-26 12:05 639233424567558554
2037 ms 79.170.43.3
35 2026-08-26 11:47 639233414056832719
80 ms 79.170.43.3
34 2026-08-26 11:30 639233403515141099
89 ms 79.170.43.3
33 2026-08-26 10:35 639233370841350248
70 ms 79.170.43.3
32 2026-08-26 10:18 639233360361507238
65 ms 79.170.43.3
31 2026-08-26 10:01 639233350067824371
43 ms 79.170.43.3
30 2026-08-26 09:43 639233339545274518
84 ms 79.170.43.3
29 2026-08-26 09:26 639233329214918079
72 ms 79.170.43.3
28 2026-08-26 09:09 639233318749762337
49 ms 79.170.43.3
27 2026-08-26 08:51 639233308387917838
83 ms 79.170.43.3
26 2026-08-26 08:34 639233297961740122
68 ms 79.170.43.3
25 2026-08-26 08:16 639233287487159094
34 ms 79.170.43.3
24 2026-08-26 07:59 639233276995531707
51 ms 79.170.43.3
23 2026-08-26 07:41 639233266521568229
91 ms 79.170.43.3
22 2026-08-26 07:24 639233256081047431
61 ms 79.170.43.3
21 2026-08-26 06:30 639233223620132921
93 ms 79.170.43.3
20 2026-08-26 06:13 639233213287814244
-
19 2026-08-26 05:55 639233202925983161
81 ms 79.170.43.3
18 2026-08-26 05:38 639233192644780696
66 ms 79.170.43.3
17 2026-08-26 05:21 639233182401183833
62 ms 79.170.43.3
16 2026-08-26 05:04 639233172074181051
48 ms 79.170.43.3
15 2026-08-26 04:47 639233161808421455
49 ms 79.170.43.3
14 2026-08-26 04:29 639233151357344052
37 ms 79.170.43.3
13 2026-08-26 04:12 639233141034116946
88 ms 79.170.43.3
12 2026-08-26 03:55 639233130828334142
99 ms 79.170.43.3
11 2026-08-26 03:38 639233120373450007
87 ms 79.170.43.3
10 2026-08-26 03:21 639233110066216193
65 ms 79.170.43.3
9 2026-08-26 02:27 639233078065410564
2043 ms 79.170.43.3
8 2026-08-26 02:10 639233067787457832
63 ms 79.170.43.3
7 2026-08-26 01:53 639233057501801162
71 ms 79.170.43.3
6 2026-08-26 01:36 639233047089431703
66 ms 79.170.43.3
5 2026-08-26 01:18 639233036754790688
73 ms 79.170.43.3
4 2026-08-26 01:01 639233026412602472
54 ms 79.170.43.3
3 2026-08-26 00:44 639233016064066127
45 ms 79.170.43.3
2 2026-08-26 00:27 639233005922655772
59 ms 79.170.43.3
1 2026-08-26 00:10 639232995672256907
63 ms 79.170.43.3