DNS response history for ns2.crf-hyper.link

ns2.crf-hyper.link 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 26 DNS check records, 26 successful responses, 0 failed responses, and 348 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.crf-hyper.link.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

348 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.33.188.145

Most recently resolved hosting IP on selected date

Successful Responses

26

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.crf-hyper.link

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
26 2026-08-25 09:05 639232451282965990
35 ms 3.33.188.145
25 2026-08-25 08:47 639232440814614938
37 ms 3.33.188.145
24 2026-08-25 08:30 639232430410720425
35 ms 3.33.188.145
23 2026-08-25 08:13 639232420003096185
17 ms 3.33.188.145
22 2026-08-25 07:55 639232409467287444
2030 ms 3.33.188.145
21 2026-08-25 07:38 639232399077195997
2109 ms 207.174.61.1
20 2026-08-25 07:21 639232388731528337
27 ms 3.33.188.145
19 2026-08-25 07:03 639232378288598612
31 ms 3.33.188.145
18 2026-08-25 06:10 639232346196373643
36 ms 3.33.188.145
17 2026-08-25 05:53 639232336112370741
55 ms 207.174.61.1
16 2026-08-25 05:36 639232326146508970
33 ms 3.33.188.145
15 2026-08-25 05:20 639232316189381720
11 ms 3.33.188.145
14 2026-08-25 05:03 639232306217998913
2022 ms 3.33.188.145
13 2026-08-25 04:46 639232296255744174
23 ms 3.33.188.145
12 2026-08-25 04:30 639232286095760789
30 ms 3.33.188.145
11 2026-08-25 04:13 639232276086186273
15 ms 3.33.188.145
10 2026-08-25 03:56 639232265900986425
20 ms 3.33.188.145
9 2026-08-25 03:39 639232255723518075
31 ms 3.33.188.145
8 2026-08-25 03:22 639232245484452890
68 ms 3.33.188.145
7 2026-08-25 03:05 639232235157175331
216 ms 3.33.188.145
6 2026-08-25 02:11 639232203197189095
19 ms 3.33.188.145
5 2026-08-25 01:54 639232192844564298
2057 ms 207.174.61.1
4 2026-08-25 01:37 639232182496008942
15 ms 3.33.188.145
3 2026-08-25 01:20 639232172197053132
16 ms 3.33.188.145
2 2026-08-25 00:26 639232140250307418
37 ms 3.33.188.145
1 2026-08-25 00:09 639232129927860324
15 ms 207.174.61.1