DNS response history for ns.clevo.com.tw

ns.clevo.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-24. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 757 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.clevo.com.tw.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

757 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

60.250.160.110

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 ns.clevo.com.tw

Showing DNS history for 2026-08-24 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-24 12:10 639231693747052549
1132 ms 60.250.160.110
28 2026-08-24 11:53 639231683712487276
249 ms 60.250.160.110
27 2026-08-24 11:37 639231673513573868
1142 ms 60.250.160.110
26 2026-08-24 10:43 639231641791249939
282 ms 60.250.160.110
25 2026-08-24 10:27 639231631866211033
995 ms 60.250.160.110
24 2026-08-24 10:10 639231621644955316
248 ms 60.250.160.110
23 2026-08-24 09:53 639231611478799259
289 ms 60.250.160.110
22 2026-08-24 09:00 639231579923718211
999 ms 60.250.160.110
21 2026-08-24 08:44 639231569810702936
252 ms 60.250.160.110
20 2026-08-24 08:27 639231559762411619
1343 ms 60.250.160.110
19 2026-08-24 08:10 639231549663595407
1181 ms 60.250.160.110
18 2026-08-24 07:17 639231518076817246
4 ms 60.250.160.110
17 2026-08-24 07:01 639231508078650885
247 ms 60.250.160.110
16 2026-08-24 06:44 639231498210697093
999 ms 60.250.160.110
15 2026-08-24 06:28 639231488109699360
1636 ms 60.250.160.110
14 2026-08-24 05:35 639231456772510692
246 ms 60.250.160.110
13 2026-08-24 05:19 639231447084631185
2 ms 60.250.160.110
12 2026-08-24 05:02 639231437208519473
2 ms 60.250.160.110
11 2026-08-24 04:46 639231427209627490
1029 ms 60.250.160.110
10 2026-08-24 03:53 639231395791246644
1142 ms 60.250.160.110
9 2026-08-24 03:37 639231386075551458
3 ms 60.250.160.110
8 2026-08-24 03:21 639231376208713791
977 ms 60.250.160.110
7 2026-08-24 03:04 639231366170589276
3152 ms 60.250.160.110
6 2026-08-24 02:12 639231334732159368
258 ms 60.250.160.110
5 2026-08-24 01:55 639231325035670078
255 ms 60.250.160.110
4 2026-08-24 01:39 639231315132253837
1892 ms 60.250.160.110
3 2026-08-24 01:22 639231305014280808
991 ms 60.250.160.110
2 2026-08-24 00:30 639231273779380675
989 ms 60.250.160.110
1 2026-08-24 00:14 639231264180839154
3 ms 60.250.160.110