DNS response history for ns2.sys-uptime.com

ns2.sys-uptime.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 216 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.sys-uptime.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

216 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.80.126.2

Most recently resolved hosting IP on selected date

Successful Responses

30

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.sys-uptime.com

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
30 2026-08-26 09:42 639233339545274518
23 ms 208.80.126.2
29 2026-08-26 09:25 639233329214918079
13 ms 208.80.126.2
28 2026-08-26 09:07 639233318749762337
9 ms 208.80.126.2
27 2026-08-26 08:50 639233308387917838
11 ms 208.80.126.2
26 2026-08-26 08:33 639233297961740122
11 ms 208.80.126.2
25 2026-08-26 08:15 639233287487159094
2038 ms 208.80.126.2
24 2026-08-26 07:58 639233276995531707
14 ms 208.80.126.2
23 2026-08-26 07:40 639233266521568229
10 ms 208.80.126.2
22 2026-08-26 07:23 639233256081047431
21 ms 208.80.126.2
21 2026-08-26 06:29 639233223620132921
13 ms 208.80.126.2
20 2026-08-26 06:11 639233213287814244
9 ms 208.80.126.2
19 2026-08-26 05:54 639233202925983161
25 ms 208.80.126.2
18 2026-08-26 05:37 639233192644780696
10 ms 208.80.126.2
17 2026-08-26 05:20 639233182401183833
11 ms 208.80.126.2
16 2026-08-26 05:03 639233172074181051
9 ms 208.80.126.2
15 2026-08-26 04:46 639233161808421455
16 ms 208.80.126.2
14 2026-08-26 04:28 639233151357344052
10 ms 208.80.126.2
13 2026-08-26 04:11 639233141034116946
17 ms 208.80.126.2
12 2026-08-26 03:54 639233130828334142
31 ms 208.80.126.2
11 2026-08-26 03:37 639233120373450007
34 ms 208.80.126.2
10 2026-08-26 03:19 639233110066216193
8 ms 208.80.126.2
9 2026-08-26 02:26 639233078065410564
14 ms 208.80.126.2
8 2026-08-26 02:09 639233067787457832
26 ms 208.80.126.2
7 2026-08-26 01:52 639233057501801162
9 ms 208.80.126.2
6 2026-08-26 01:34 639233047089431703
10 ms 208.80.126.2
5 2026-08-26 01:17 639233036754790688
4014 ms 208.80.126.2
4 2026-08-26 01:00 639233026412602472
10 ms 208.80.126.2
3 2026-08-26 00:43 639233016064066127
20 ms 208.80.126.2
2 2026-08-26 00:26 639233005922655772
20 ms 208.80.126.2
1 2026-08-26 00:09 639232995672256907
9 ms 208.80.126.2