DNS response history for ns1.neckers.net

ns1.neckers.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 218 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 ns1.neckers.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

218 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.29.138.139

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns1.neckers.net

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
34 2026-08-24 14:10 639231765923559455
304 ms 66.29.138.139
33 2026-08-24 13:54 639231755868832964
326 ms 66.29.138.139
32 2026-08-24 13:37 639231745628278877
316 ms 66.29.138.139
31 2026-08-24 13:20 639231735407682062
314 ms 66.29.138.139
30 2026-08-24 12:27 639231703815441688
318 ms 66.29.138.139
29 2026-08-24 12:10 639231693747052549
303 ms 66.29.138.139
28 2026-08-24 11:53 639231683712487276
315 ms 66.29.138.139
27 2026-08-24 11:37 639231673513573868
258 ms 66.29.138.139
26 2026-08-24 10:43 639231641791249939
297 ms 66.29.138.139
25 2026-08-24 10:27 639231631866211033
2 ms 66.29.138.139
24 2026-08-24 10:10 639231621644955316
3 ms 66.29.138.139
23 2026-08-24 09:53 639231611478799259
309 ms 66.29.138.139
22 2026-08-24 09:00 639231579923718211
4 ms 66.29.138.139
21 2026-08-24 08:44 639231569810702936
298 ms 66.29.138.139
20 2026-08-24 08:27 639231559762411619
312 ms 66.29.138.139
19 2026-08-24 08:10 639231549663595407
299 ms 66.29.138.139
18 2026-08-24 07:17 639231518076817246
306 ms 66.29.138.139
17 2026-08-24 07:01 639231508078650885
305 ms 66.29.138.139
16 2026-08-24 06:44 639231498210697093
210 ms 66.29.138.139
15 2026-08-24 06:27 639231488109699360
303 ms 66.29.138.139
14 2026-08-24 05:35 639231456772510692
158 ms 66.29.138.139
13 2026-08-24 05:19 639231447084631185
3 ms 66.29.138.139
12 2026-08-24 05:02 639231437208519473
3 ms 66.29.138.139
11 2026-08-24 04:46 639231427209627490
295 ms 66.29.138.139
10 2026-08-24 03:53 639231395791246644
3 ms 66.29.138.139
9 2026-08-24 03:37 639231386075551458
302 ms 66.29.138.139
8 2026-08-24 03:21 639231376208713791
312 ms 66.29.138.139
7 2026-08-24 03:04 639231366170589276
303 ms 66.29.138.139
6 2026-08-24 02:12 639231334732159368
302 ms 66.29.138.139
5 2026-08-24 01:55 639231325035670078
2 ms 66.29.138.139
4 2026-08-24 01:39 639231315132253837
327 ms 66.29.138.139
3 2026-08-24 01:22 639231305014280808
2 ms 66.29.138.139
2 2026-08-24 00:30 639231273779380675
306 ms 66.29.138.139
1 2026-08-24 00:14 639231264180839154
3 ms 66.29.138.139