DNS response history for hcrt.com.tw

hcrt.com.tw 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 29 DNS check records, 29 successful responses, 0 failed responses, and 606 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 hcrt.com.tw.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

606 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.120.66.197

Most recently resolved hosting IP on selected date

Successful Responses

29

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 hcrt.com.tw

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
29 2026-08-25 09:47 639232471861770303
580 ms 59.120.66.197
28 2026-08-25 09:30 639232461630217327
577 ms 59.120.66.197
27 2026-08-25 09:13 639232451282965990
586 ms 59.120.66.197
26 2026-08-25 08:55 639232440814614938
742 ms 59.120.66.197
25 2026-08-25 08:38 639232430410720425
596 ms 59.120.66.197
24 2026-08-25 08:21 639232420003096185
690 ms 59.120.66.197
23 2026-08-25 08:03 639232409467287444
589 ms 59.120.66.197
22 2026-08-25 07:46 639232399077195997
739 ms 59.120.66.197
21 2026-08-25 07:28 639232388731528337
571 ms 59.120.66.197
20 2026-08-25 07:11 639232378288598612
587 ms 59.120.66.197
19 2026-08-25 06:17 639232346196373643
595 ms 59.120.66.197
18 2026-08-25 06:00 639232336112370741
586 ms 59.120.66.197
17 2026-08-25 05:44 639232326146508970
615 ms 59.120.66.197
16 2026-08-25 05:27 639232316189381720
715 ms 59.120.66.197
15 2026-08-25 05:11 639232306217998913
574 ms 59.120.66.197
14 2026-08-25 04:54 639232296255744174
594 ms 59.120.66.197
13 2026-08-25 04:37 639232286095760789
259 ms 59.120.66.197
12 2026-08-25 04:20 639232276086186273
574 ms 59.120.66.197
11 2026-08-25 04:04 639232265900986425
573 ms 59.120.66.197
10 2026-08-25 03:47 639232255723518075
589 ms 59.120.66.197
9 2026-08-25 03:30 639232245484452890
587 ms 59.120.66.197
8 2026-08-25 03:12 639232235157175331
566 ms 59.120.66.197
7 2026-08-25 02:19 639232203197189095
576 ms 59.120.66.197
6 2026-08-25 02:02 639232192844564298
693 ms 59.120.66.197
5 2026-08-25 01:45 639232182496008942
731 ms 59.120.66.197
4 2026-08-25 01:27 639232172197053132
584 ms 59.120.66.197
3 2026-08-25 00:34 639232140250307418
754 ms 59.120.66.197
2 2026-08-25 00:17 639232129927860324
578 ms 59.120.66.197
1 2026-08-25 00:00 639232119551972438
570 ms 59.120.66.197