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-29. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 467 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

29

Historical checks stored for this nameserver on selected date

Average Latency

467 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 10:35

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

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 ns2.highlevel.com.tw

Showing DNS history for 2026-08-29 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-29 10:35 639235956590882003
701 ms 211.20.201.122
28 2026-08-29 09:41 639235924465736791
271 ms 211.20.201.122
27 2026-08-29 09:24 639235914430611197
585 ms 211.20.201.122
26 2026-08-29 09:07 639235904343784853
2325 ms 211.20.201.122
25 2026-08-29 08:51 639235894201078068
3 ms 211.20.201.122
24 2026-08-29 08:34 639235884233447452
3 ms 211.20.201.122
23 2026-08-29 08:17 639235874142207309
603 ms 211.20.201.122
22 2026-08-29 08:00 639235863974652466
590 ms 211.20.201.122
21 2026-08-29 07:43 639235853716243436
3 ms 211.20.201.122
20 2026-08-29 07:26 639235843614494759
589 ms 211.20.201.122
19 2026-08-29 07:09 639235833401459551
595 ms 211.20.201.122
18 2026-08-29 06:52 639235823220464528
584 ms 211.20.201.122
17 2026-08-29 06:35 639235812997510905
3 ms 211.20.201.122
16 2026-08-29 05:42 639235781101962521
3 ms 211.20.201.122
15 2026-08-29 05:25 639235771207673260
590 ms 211.20.201.122
14 2026-08-29 05:09 639235761047429642
3 ms 211.20.201.122
13 2026-08-29 04:52 639235750964347246
1020 ms 211.20.201.122
12 2026-08-29 04:35 639235740923490874
3 ms 211.20.201.122
11 2026-08-29 04:18 639235730842894399
597 ms 211.20.201.122
10 2026-08-29 04:01 639235720760084717
3 ms 211.20.201.122
9 2026-08-29 03:45 639235710843666743
605 ms 211.20.201.122
8 2026-08-29 03:28 639235700733510561
590 ms 211.20.201.122
7 2026-08-29 03:11 639235690509906192
3 ms 211.20.201.122
6 2026-08-29 02:54 639235680156673501
3 ms 211.20.201.122
5 2026-08-29 02:37 639235669720606443
609 ms 211.20.201.122
4 2026-08-29 01:43 639235637451417084
590 ms 211.20.201.122
3 2026-08-29 01:26 639235627307383453
589 ms 211.20.201.122
2 2026-08-29 01:09 639235616906386856
744 ms 211.20.201.122
1 2026-08-29 00:51 639235606582912691
739 ms 211.20.201.122