DNS response history for ns1.dingzhi.store

ns1.dingzhi.store 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, 29 successful responses, 1 failed responses, and 291 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.dingzhi.store.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

291 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

188.209.136.50

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.dingzhi.store

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:18 639231703815441688
104 ms 188.209.136.50
29 2026-08-24 12:01 639231693747052549
81 ms 188.209.136.50
28 2026-08-24 11:44 639231683712487276
132 ms 188.209.136.50
27 2026-08-24 11:27 639231673513573868
99 ms 188.209.136.50
26 2026-08-24 10:34 639231641791249939
89 ms 188.209.136.50
25 2026-08-24 10:18 639231631866211033
115 ms 188.209.136.50
24 2026-08-24 10:01 639231621644955316
2053 ms 188.209.136.50
23 2026-08-24 09:44 639231611478799259
86 ms 188.209.136.50
22 2026-08-24 08:51 639231579923718211
10 ms 188.209.136.50
21 2026-08-24 08:34 639231569810702936
98 ms 188.209.136.50
20 2026-08-24 08:17 639231559762411619
142 ms 188.209.136.50
19 2026-08-24 08:01 639231549663595407
94 ms 188.209.136.50
18 2026-08-24 07:08 639231518076817246
4 ms 188.209.136.50
17 2026-08-24 06:52 639231508078650885
53 ms 188.209.136.50
16 2026-08-24 06:35 639231498210697093
90 ms 188.209.136.50
15 2026-08-24 06:18 639231488109699360
90 ms 188.209.136.50
14 2026-08-24 05:26 639231456772510692
97 ms 188.209.136.50
13 2026-08-24 05:10 639231447084631185
63 ms 188.209.136.50
12 2026-08-24 04:53 639231437208519473
91 ms 188.209.136.50
11 2026-08-24 04:37 639231427209627490
71 ms 188.209.136.50
10 2026-08-24 03:44 639231395791246644
85 ms 188.209.136.50
9 2026-08-24 03:28 639231386075551458
14 ms 188.209.136.50
8 2026-08-24 03:12 639231376208713791
2093 ms 188.209.136.50
7 2026-08-24 02:55 639231366170589276
91 ms 188.209.136.50
6 2026-08-24 02:03 639231334732159368
139 ms 188.209.136.50
5 2026-08-24 01:46 639231325035670078
109 ms 188.209.136.50
4 2026-08-24 01:30 639231315132253837
83 ms 188.209.136.50
3 2026-08-24 01:13 639231305014280808
100 ms 188.209.136.50
2 2026-08-24 00:21 639231273779380675
-
1 2026-08-24 00:05 639231264180839154
2058 ms 188.209.136.50