DNS response history for ns2.null.cn

ns2.null.cn 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 685 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.null.cn.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

685 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

170.33.12.185

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.null.cn

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:54 639231828211839931
1416 ms 170.33.12.185
37 2026-08-24 15:37 639231818080917481
901 ms 170.33.12.185
36 2026-08-24 15:20 639231807961539652
705 ms 170.33.12.185
35 2026-08-24 15:03 639231797631669865
581 ms 170.33.12.185
34 2026-08-24 14:10 639231765923559455
677 ms 170.33.12.185
33 2026-08-24 13:54 639231755868832964
618 ms 170.33.12.185
32 2026-08-24 13:37 639231745628278877
716 ms 170.33.12.185
31 2026-08-24 13:19 639231735407682062
850 ms 170.33.12.185
30 2026-08-24 12:27 639231703815441688
557 ms 170.33.12.185
29 2026-08-24 12:10 639231693747052549
287 ms 170.33.12.185
28 2026-08-24 11:53 639231683712487276
794 ms 170.33.12.185
27 2026-08-24 11:36 639231673513573868
580 ms 170.33.12.185
26 2026-08-24 10:43 639231641791249939
919 ms 170.33.12.185
25 2026-08-24 10:27 639231631866211033
374 ms 170.33.12.185
24 2026-08-24 10:10 639231621644955316
452 ms 170.33.12.185
23 2026-08-24 09:53 639231611478799259
544 ms 170.33.12.185
22 2026-08-24 09:00 639231579923718211
946 ms 170.33.12.185
21 2026-08-24 08:44 639231569810702936
376 ms 170.33.12.185
20 2026-08-24 08:27 639231559762411619
273 ms 170.33.12.185
19 2026-08-24 08:10 639231549663595407
594 ms 170.33.12.185
18 2026-08-24 07:17 639231518076817246
267 ms 170.33.12.185
17 2026-08-24 07:01 639231508078650885
550 ms 170.33.12.185
16 2026-08-24 06:44 639231498210697093
1199 ms 170.33.12.185
15 2026-08-24 06:27 639231488109699360
975 ms 170.33.12.185
14 2026-08-24 05:35 639231456772510692
502 ms 170.33.12.185
13 2026-08-24 05:19 639231447084631185
280 ms 170.33.12.185
12 2026-08-24 05:02 639231437208519473
949 ms 170.33.12.185
11 2026-08-24 04:46 639231427209627490
586 ms 170.33.12.185
10 2026-08-24 03:53 639231395791246644
2438 ms 170.33.12.185
9 2026-08-24 03:37 639231386075551458
501 ms 170.33.12.185
8 2026-08-24 03:21 639231376208713791
777 ms 170.33.12.185
7 2026-08-24 03:04 639231366170589276
279 ms 170.33.12.185
6 2026-08-24 02:12 639231334732159368
549 ms 170.33.12.185
5 2026-08-24 01:55 639231325035670078
749 ms 170.33.12.185
4 2026-08-24 01:39 639231315132253837
516 ms 170.33.12.185
3 2026-08-24 01:22 639231305014280808
537 ms 170.33.12.185
2 2026-08-24 00:30 639231273779380675
490 ms 170.33.12.185
1 2026-08-24 00:14 639231264180839154
742 ms 170.33.12.185