DNS response history for ns1.neokron.com

ns1.neokron.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 323 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.neokron.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

323 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.204.121

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 ns1.neokron.com

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
30 2026-08-24 12:22 639231703815441688
3 ms 51.222.204.121
29 2026-08-24 12:05 639231693747052549
113 ms 51.222.204.121
28 2026-08-24 11:48 639231683712487276
236 ms 51.222.204.121
27 2026-08-24 11:31 639231673513573868
228 ms 51.222.204.121
26 2026-08-24 10:38 639231641791249939
175 ms 51.222.204.121
25 2026-08-24 10:22 639231631866211033
5 ms 51.222.204.121
24 2026-08-24 10:05 639231621644955316
235 ms 51.222.204.121
23 2026-08-24 09:48 639231611478799259
110 ms 51.222.204.121
22 2026-08-24 08:55 639231579923718211
111 ms 51.222.204.121
21 2026-08-24 08:39 639231569810702936
232 ms 51.222.204.121
20 2026-08-24 08:21 639231559762411619
8 ms 51.222.204.121
19 2026-08-24 08:05 639231549663595407
2287 ms 51.222.204.121
18 2026-08-24 07:12 639231518076817246
107 ms 51.222.204.121
17 2026-08-24 06:56 639231508078650885
8 ms 51.222.204.121
16 2026-08-24 06:39 639231498210697093
7 ms 51.222.204.121
15 2026-08-24 06:22 639231488109699360
103 ms 51.222.204.121
14 2026-08-24 05:30 639231456772510692
124 ms 51.222.204.121
13 2026-08-24 05:14 639231447084631185
109 ms 51.222.204.121
12 2026-08-24 04:57 639231437208519473
216 ms 51.222.204.121
11 2026-08-24 04:41 639231427209627490
215 ms 51.222.204.121
10 2026-08-24 03:48 639231395791246644
232 ms 51.222.204.121
9 2026-08-24 03:32 639231386075551458
2218 ms 51.222.204.121
8 2026-08-24 03:16 639231376208713791
220 ms 51.222.204.121
7 2026-08-24 02:59 639231366170589276
9 ms 51.222.204.121
6 2026-08-24 02:07 639231334732159368
12 ms 51.222.204.121
5 2026-08-24 01:50 639231325035670078
8 ms 51.222.204.121
4 2026-08-24 01:34 639231315132253837
108 ms 51.222.204.121
3 2026-08-24 01:17 639231305014280808
103 ms 51.222.204.121
2 2026-08-24 00:25 639231273779380675
2015 ms 51.222.204.121
1 2026-08-24 00:09 639231264180839154
132 ms 51.222.204.121