DNS response history for ns2.zcodesports.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

147 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.88.81.24

Most recently resolved hosting IP on selected date

Successful Responses

39

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.zcodesports.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
39 2026-08-24 16:40 639231860258429562
126 ms 23.88.81.24
38 2026-08-24 15:47 639231828211839931
51 ms 23.88.81.24
37 2026-08-24 15:30 639231818080917481
38 ms 23.88.81.24
36 2026-08-24 15:13 639231807961539652
39 ms 23.88.81.24
35 2026-08-24 14:56 639231797631669865
31 ms 23.88.81.24
34 2026-08-24 14:03 639231765923559455
21 ms 23.88.81.24
33 2026-08-24 13:46 639231755868832964
42 ms 23.88.81.24
32 2026-08-24 13:29 639231745628278877
8 ms 23.88.81.24
31 2026-08-24 13:12 639231735407682062
48 ms 23.88.81.24
30 2026-08-24 12:19 639231703815441688
47 ms 23.88.81.24
29 2026-08-24 12:03 639231693747052549
2026 ms 23.88.81.24
28 2026-08-24 11:46 639231683712487276
7 ms 23.88.81.24
27 2026-08-24 11:29 639231673513573868
52 ms 23.88.81.24
26 2026-08-24 10:36 639231641791249939
33 ms 23.88.81.24
25 2026-08-24 10:19 639231631866211033
196 ms 23.88.81.24
24 2026-08-24 10:03 639231621644955316
27 ms 23.88.81.24
23 2026-08-24 09:46 639231611478799259
34 ms 23.88.81.24
22 2026-08-24 08:53 639231579923718211
51 ms 23.88.81.24
21 2026-08-24 08:36 639231569810702936
49 ms 23.88.81.24
20 2026-08-24 08:19 639231559762411619
67 ms 23.88.81.24
19 2026-08-24 08:03 639231549663595407
55 ms 23.88.81.24
18 2026-08-24 07:10 639231518076817246
15 ms 23.88.81.24
17 2026-08-24 06:54 639231508078650885
45 ms 23.88.81.24
16 2026-08-24 06:37 639231498210697093
70 ms 23.88.81.24
15 2026-08-24 06:20 639231488109699360
3 ms 23.88.81.24
14 2026-08-24 05:28 639231456772510692
39 ms 23.88.81.24
13 2026-08-24 05:12 639231447084631185
50 ms 23.88.81.24
12 2026-08-24 04:55 639231437208519473
38 ms 23.88.81.24
11 2026-08-24 04:38 639231427209627490
44 ms 23.88.81.24
10 2026-08-24 03:46 639231395791246644
10 ms 23.88.81.24
9 2026-08-24 03:30 639231386075551458
32 ms 23.88.81.24
8 2026-08-24 03:14 639231376208713791
35 ms 23.88.81.24
7 2026-08-24 02:57 639231366170589276
43 ms 23.88.81.24
6 2026-08-24 02:05 639231334732159368
33 ms 23.88.81.24
5 2026-08-24 01:48 639231325035670078
55 ms 23.88.81.24
4 2026-08-24 01:32 639231315132253837
53 ms 23.88.81.24
3 2026-08-24 01:15 639231305014280808
53 ms 23.88.81.24
2 2026-08-24 00:23 639231273779380675
8 ms 23.88.81.24
1 2026-08-24 00:07 639231264180839154
2075 ms 23.88.81.24