DNS response history for ns2.highlevel.com.tw

ns2.highlevel.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 22 DNS check records, 22 successful responses, 0 failed responses, and 637 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.highlevel.com.tw.
Records on Selected Date

22

Historical checks stored for this nameserver on selected date

Average Latency

637 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 06:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.20.201.122

Most recently resolved hosting IP on selected date

Successful Responses

22

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.highlevel.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
22 2026-08-26 06:40 639233223620132921
773 ms 211.20.201.122
21 2026-08-26 06:23 639233213287814244
595 ms 211.20.201.122
20 2026-08-26 06:05 639233202925983161
596 ms 211.20.201.122
19 2026-08-26 05:48 639233192644780696
586 ms 211.20.201.122
18 2026-08-26 05:31 639233182401183833
709 ms 211.20.201.122
17 2026-08-26 05:14 639233172074181051
614 ms 211.20.201.122
16 2026-08-26 04:57 639233161808421455
754 ms 211.20.201.122
15 2026-08-26 04:40 639233151357344052
597 ms 211.20.201.122
14 2026-08-26 04:22 639233141034116946
587 ms 211.20.201.122
13 2026-08-26 04:05 639233130828334142
724 ms 211.20.201.122
12 2026-08-26 03:48 639233120373450007
625 ms 211.20.201.122
11 2026-08-26 03:30 639233110066216193
611 ms 211.20.201.122
10 2026-08-26 02:37 639233078065410564
595 ms 211.20.201.122
9 2026-08-26 02:20 639233067787457832
593 ms 211.20.201.122
8 2026-08-26 02:03 639233057501801162
578 ms 211.20.201.122
7 2026-08-26 01:46 639233047089431703
579 ms 211.20.201.122
6 2026-08-26 01:28 639233036754790688
581 ms 211.20.201.122
5 2026-08-26 01:11 639233026412602472
607 ms 211.20.201.122
4 2026-08-26 00:54 639233016064066127
752 ms 211.20.201.122
3 2026-08-26 00:37 639233005922655772
621 ms 211.20.201.122
2 2026-08-26 00:20 639232995672256907
738 ms 211.20.201.122
1 2026-08-26 00:03 639232985300872416
598 ms 211.20.201.122