DNS response history for ns2.nextkodem.com

ns2.nextkodem.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 38 DNS check records, 38 successful responses, 0 failed responses, and 1563 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.nextkodem.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

1563 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

2.57.91.92

Most recently resolved hosting IP on selected date

Successful Responses

38

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.nextkodem.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
38 2026-08-24 15:56 639231828211839931
2029 ms 2.57.91.92
37 2026-08-24 15:39 639231818080917481
2022 ms 2.57.91.92
36 2026-08-24 15:22 639231807961539652
2034 ms 2.57.91.92
35 2026-08-24 15:05 639231797631669865
3 ms 2.57.91.92
34 2026-08-24 14:12 639231765923559455
2064 ms 2.57.91.92
33 2026-08-24 13:55 639231755868832964
2022 ms 2.57.91.92
32 2026-08-24 13:38 639231745628278877
2033 ms 2.57.91.92
31 2026-08-24 13:21 639231735407682062
2010 ms 2.57.91.92
30 2026-08-24 12:28 639231703815441688
2175 ms 2.57.91.92
29 2026-08-24 12:12 639231693747052549
2021 ms 2.57.91.92
28 2026-08-24 11:55 639231683712487276
2023 ms 2.57.91.92
27 2026-08-24 11:38 639231673513573868
2022 ms 2.57.91.92
26 2026-08-24 10:45 639231641791249939
2031 ms 2.57.91.92
25 2026-08-24 10:28 639231631866211033
2 ms 2.57.91.92
24 2026-08-24 10:12 639231621644955316
2193 ms 2.57.91.92
23 2026-08-24 09:55 639231611478799259
2022 ms 2.57.91.92
22 2026-08-24 09:02 639231579923718211
3 ms 2.57.91.92
21 2026-08-24 08:45 639231569810702936
5 ms 2.57.91.92
20 2026-08-24 08:28 639231559762411619
2170 ms 2.57.91.92
19 2026-08-24 08:12 639231549663595407
2042 ms 2.57.91.92
18 2026-08-24 07:18 639231518076817246
2 ms 2.57.91.92
17 2026-08-24 07:02 639231508078650885
2188 ms 2.57.91.92
16 2026-08-24 06:45 639231498210697093
3692 ms 2.57.91.92
15 2026-08-24 06:29 639231488109699360
2021 ms 2.57.91.92
14 2026-08-24 05:36 639231456772510692
3 ms 2.57.91.92
13 2026-08-24 05:20 639231447084631185
3 ms 2.57.91.92
12 2026-08-24 05:04 639231437208519473
3 ms 2.57.91.92
11 2026-08-24 04:47 639231427209627490
2011 ms 2.57.91.92
10 2026-08-24 03:54 639231395791246644
4 ms 2.57.91.92
9 2026-08-24 03:38 639231386075551458
2030 ms 2.57.91.92
8 2026-08-24 03:22 639231376208713791
2229 ms 2.57.91.92
7 2026-08-24 03:06 639231366170589276
4024 ms 2.57.91.92
6 2026-08-24 02:13 639231334732159368
3 ms 2.57.91.92
5 2026-08-24 01:57 639231325035670078
3 ms 2.57.91.92
4 2026-08-24 01:40 639231315132253837
2023 ms 2.57.91.92
3 2026-08-24 01:24 639231305014280808
2162 ms 2.57.91.92
2 2026-08-24 00:31 639231273779380675
2028 ms 2.57.91.92
1 2026-08-24 00:15 639231264180839154
2028 ms 2.57.91.92