DNS response history for ns1.chaindiscovering.com

ns1.chaindiscovering.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 240 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.chaindiscovering.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

240 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.72.106.225

Most recently resolved hosting IP on selected date

Successful Responses

36

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.chaindiscovering.com

Showing DNS history for 2026-08-26 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
36 2026-08-26 12:02 639233424567558554
2051 ms 94.72.106.225
35 2026-08-26 11:45 639233414056832719
85 ms 94.72.106.225
34 2026-08-26 11:27 639233403515141099
67 ms 94.72.106.225
33 2026-08-26 10:33 639233370841350248
81 ms 94.72.106.225
32 2026-08-26 10:15 639233360361507238
2053 ms 94.72.106.225
31 2026-08-26 09:58 639233350067824371
79 ms 94.72.106.225
30 2026-08-26 09:41 639233339545274518
101 ms 94.72.106.225
29 2026-08-26 09:23 639233329214918079
34 ms 94.72.106.225
28 2026-08-26 09:06 639233318749762337
105 ms 94.72.106.225
27 2026-08-26 08:49 639233308387917838
64 ms 94.72.106.225
26 2026-08-26 08:31 639233297961740122
57 ms 94.72.106.225
25 2026-08-26 08:14 639233287487159094
97 ms 94.72.106.225
24 2026-08-26 07:56 639233276995531707
89 ms 94.72.106.225
23 2026-08-26 07:39 639233266521568229
120 ms 94.72.106.225
22 2026-08-26 07:22 639233256081047431
82 ms 94.72.106.225
21 2026-08-26 06:27 639233223620132921
43 ms 94.72.106.225
20 2026-08-26 06:10 639233213287814244
2058 ms 94.72.106.225
19 2026-08-26 05:53 639233202925983161
80 ms 94.72.106.225
18 2026-08-26 05:36 639233192644780696
34 ms 94.72.106.225
17 2026-08-26 05:19 639233182401183833
32 ms 94.72.106.225
16 2026-08-26 05:02 639233172074181051
61 ms 94.72.106.225
15 2026-08-26 04:44 639233161808421455
45 ms 94.72.106.225
14 2026-08-26 04:27 639233151357344052
88 ms 94.72.106.225
13 2026-08-26 04:10 639233141034116946
236 ms 94.72.106.225
12 2026-08-26 03:53 639233130828334142
59 ms 94.72.106.225
11 2026-08-26 03:35 639233120373450007
35 ms 94.72.106.225
10 2026-08-26 03:18 639233110066216193
97 ms 94.72.106.225
9 2026-08-26 02:25 639233078065410564
29 ms 94.72.106.225
8 2026-08-26 02:08 639233067787457832
73 ms 94.72.106.225
7 2026-08-26 01:51 639233057501801162
60 ms 94.72.106.225
6 2026-08-26 01:33 639233047089431703
61 ms 94.72.106.225
5 2026-08-26 01:16 639233036754790688
63 ms 94.72.106.225
4 2026-08-26 00:59 639233026412602472
66 ms 94.72.106.225
3 2026-08-26 00:41 639233016064066127
59 ms 94.72.106.225
2 2026-08-26 00:25 639233005922655772
40 ms 94.72.106.225
1 2026-08-26 00:07 639232995672256907
155 ms 94.72.106.225