DNS response history for ns.juth.com.tw

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

36

Historical checks stored for this nameserver on selected date

Average Latency

595 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.130.180.108

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 ns.juth.com.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
36 2026-08-26 11:58 639233414056832719
725 ms 220.130.180.108
35 2026-08-26 11:40 639233403515141099
772 ms 220.130.180.108
34 2026-08-26 10:46 639233370841350248
705 ms 220.130.180.108
33 2026-08-26 10:28 639233360361507238
739 ms 220.130.180.108
32 2026-08-26 10:11 639233350067824371
593 ms 220.130.180.108
31 2026-08-26 09:54 639233339545274518
707 ms 220.130.180.108
30 2026-08-26 09:36 639233329214918079
578 ms 220.130.180.108
29 2026-08-26 09:19 639233318749762337
612 ms 220.130.180.108
28 2026-08-26 09:02 639233308387917838
610 ms 220.130.180.108
27 2026-08-26 08:44 639233297961740122
793 ms 220.130.180.108
26 2026-08-26 08:27 639233287487159094
588 ms 220.130.180.108
25 2026-08-26 08:09 639233276995531707
610 ms 220.130.180.108
24 2026-08-26 07:52 639233266521568229
732 ms 220.130.180.108
23 2026-08-26 07:34 639233256081047431
749 ms 220.130.180.108
22 2026-08-26 06:40 639233223620132921
735 ms 220.130.180.108
21 2026-08-26 06:23 639233213287814244
731 ms 220.130.180.108
20 2026-08-26 06:06 639233202925983161
593 ms 220.130.180.108
19 2026-08-26 05:49 639233192644780696
584 ms 220.130.180.108
18 2026-08-26 05:31 639233182401183833
651 ms 220.130.180.108
17 2026-08-26 05:14 639233172074181051
4 ms 220.130.180.108
16 2026-08-26 04:57 639233161808421455
717 ms 220.130.180.108
15 2026-08-26 04:40 639233151357344052
586 ms 220.130.180.108
14 2026-08-26 04:23 639233141034116946
597 ms 220.130.180.108
13 2026-08-26 04:05 639233130828334142
3 ms 220.130.180.108
12 2026-08-26 03:48 639233120373450007
601 ms 220.130.180.108
11 2026-08-26 03:31 639233110066216193
583 ms 220.130.180.108
10 2026-08-26 02:38 639233078065410564
605 ms 220.130.180.108
9 2026-08-26 02:21 639233067787457832
594 ms 220.130.180.108
8 2026-08-26 02:03 639233057501801162
575 ms 220.130.180.108
7 2026-08-26 01:46 639233047089431703
3 ms 220.130.180.108
6 2026-08-26 01:29 639233036754790688
593 ms 220.130.180.108
5 2026-08-26 01:12 639233026412602472
602 ms 220.130.180.108
4 2026-08-26 00:54 639233016064066127
620 ms 220.130.180.108
3 2026-08-26 00:37 639233005922655772
576 ms 220.130.180.108
2 2026-08-26 00:20 639232995672256907
762 ms 220.130.180.108
1 2026-08-26 00:03 639232985300872416
604 ms 220.130.180.108