DNS response history for ns1.hct.tw

ns1.hct.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 648 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.hct.tw.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

648 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

125.227.74.212

Most recently resolved hosting IP on selected date

Successful Responses

30

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.hct.tw

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
30 2026-08-26 09:36 639233329214918079
300 ms 125.227.74.212
29 2026-08-26 09:19 639233318749762337
2423 ms 125.227.74.212
28 2026-08-26 09:01 639233308387917838
616 ms 125.227.74.212
27 2026-08-26 08:44 639233297961740122
600 ms 125.227.74.212
26 2026-08-26 08:26 639233287487159094
302 ms 125.227.74.212
25 2026-08-26 08:09 639233276995531707
314 ms 125.227.74.212
24 2026-08-26 07:51 639233266521568229
607 ms 125.227.74.212
23 2026-08-26 07:34 639233256081047431
590 ms 125.227.74.212
22 2026-08-26 06:40 639233223620132921
597 ms 125.227.74.212
21 2026-08-26 06:23 639233213287814244
292 ms 125.227.74.212
20 2026-08-26 06:05 639233202925983161
627 ms 125.227.74.212
19 2026-08-26 05:48 639233192644780696
611 ms 125.227.74.212
18 2026-08-26 05:31 639233182401183833
608 ms 125.227.74.212
17 2026-08-26 05:14 639233172074181051
706 ms 125.227.74.212
16 2026-08-26 04:57 639233161808421455
301 ms 125.227.74.212
15 2026-08-26 04:39 639233151357344052
2 ms 125.227.74.212
14 2026-08-26 04:22 639233141034116946
619 ms 125.227.74.212
13 2026-08-26 04:05 639233130828334142
609 ms 125.227.74.212
12 2026-08-26 03:48 639233120373450007
738 ms 125.227.74.212
11 2026-08-26 03:30 639233110066216193
729 ms 125.227.74.212
10 2026-08-26 02:37 639233078065410564
5 ms 125.227.74.212
9 2026-08-26 02:20 639233067787457832
3 ms 125.227.74.212
8 2026-08-26 02:03 639233057501801162
2603 ms 125.227.74.212
7 2026-08-26 01:46 639233047089431703
733 ms 125.227.74.212
6 2026-08-26 01:28 639233036754790688
677 ms 125.227.74.212
5 2026-08-26 01:11 639233026412602472
691 ms 125.227.74.212
4 2026-08-26 00:54 639233016064066127
599 ms 125.227.74.212
3 2026-08-26 00:37 639233005922655772
616 ms 125.227.74.212
2 2026-08-26 00:20 639232995672256907
736 ms 125.227.74.212
1 2026-08-26 00:03 639232985300872416
597 ms 125.227.74.212