DNS response history for ns1.classiccryptochorus.net

ns1.classiccryptochorus.net 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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 2126 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.classiccryptochorus.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

2126 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

70.98.78.230

Most recently resolved hosting IP on selected date

Successful Responses

31

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.classiccryptochorus.net

Showing DNS history for 2026-08-25 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
31 2026-08-25 10:23 639232492740373468
2186 ms 70.98.78.230
30 2026-08-25 10:06 639232482235303141
2198 ms 70.98.78.230
29 2026-08-25 09:48 639232471861770303
2033 ms 70.98.78.230
28 2026-08-25 09:31 639232461630217327
2034 ms 70.98.78.230
27 2026-08-25 09:14 639232451282965990
2158 ms 70.98.78.230
26 2026-08-25 08:57 639232440814614938
4187 ms 70.98.78.230
25 2026-08-25 08:39 639232430410720425
2159 ms 70.98.78.230
24 2026-08-25 08:22 639232420003096185
2162 ms 70.98.78.230
23 2026-08-25 08:05 639232409467287444
2160 ms 70.98.78.230
22 2026-08-25 07:47 639232399077195997
2185 ms 70.98.78.230
21 2026-08-25 07:30 639232388731528337
2233 ms 70.98.78.230
20 2026-08-25 07:13 639232378288598612
2008 ms 70.98.78.230
19 2026-08-25 06:19 639232346196373643
2034 ms 70.98.78.230
18 2026-08-25 06:02 639232336112370741
2156 ms 70.98.78.230
17 2026-08-25 05:45 639232326146508970
2165 ms 70.98.78.230
16 2026-08-25 05:28 639232316189381720
2009 ms 70.98.78.230
15 2026-08-25 05:12 639232306217998913
4 ms 70.98.78.230
14 2026-08-25 04:55 639232296255744174
2031 ms 70.98.78.230
13 2026-08-25 04:39 639232286095760789
2203 ms 70.98.78.230
12 2026-08-25 04:22 639232276086186273
2165 ms 70.98.78.230
11 2026-08-25 04:05 639232265900986425
2010 ms 70.98.78.230
10 2026-08-25 03:48 639232255723518075
2035 ms 70.98.78.230
9 2026-08-25 03:31 639232245484452890
2161 ms 70.98.78.230
8 2026-08-25 03:14 639232235157175331
2200 ms 70.98.78.230
7 2026-08-25 02:20 639232203197189095
2155 ms 70.98.78.230
6 2026-08-25 02:04 639232192844564298
2196 ms 70.98.78.230
5 2026-08-25 01:46 639232182496008942
2159 ms 70.98.78.230
4 2026-08-25 01:29 639232172197053132
4160 ms 70.98.78.230
3 2026-08-25 00:35 639232140250307418
2207 ms 70.98.78.230
2 2026-08-25 00:19 639232129927860324
2159 ms 70.98.78.230
1 2026-08-25 00:01 639232119551972438
2 ms 70.98.78.230