DNS response history for ns.cnslaw.tw

ns.cnslaw.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 30 DNS check records, 30 successful responses, 0 failed responses, and 471 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.cnslaw.tw.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

471 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

124.150.132.80

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 ns.cnslaw.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
30 2026-08-24 12:27 639231703815441688
4 ms 124.150.132.80
29 2026-08-24 12:11 639231693747052549
4 ms 124.150.132.80
28 2026-08-24 11:54 639231683712487276
585 ms 124.150.132.80
27 2026-08-24 11:37 639231673513573868
1202 ms 124.150.132.80
26 2026-08-24 10:44 639231641791249939
5 ms 124.150.132.80
25 2026-08-24 10:27 639231631866211033
2 ms 124.150.132.80
24 2026-08-24 10:11 639231621644955316
607 ms 124.150.132.80
23 2026-08-24 09:54 639231611478799259
1807 ms 124.150.132.80
22 2026-08-24 09:01 639231579923718211
4 ms 124.150.132.80
21 2026-08-24 08:44 639231569810702936
1232 ms 124.150.132.80
20 2026-08-24 08:27 639231559762411619
1211 ms 124.150.132.80
19 2026-08-24 08:10 639231549663595407
3 ms 124.150.132.80
18 2026-08-24 07:18 639231518076817246
1217 ms 124.150.132.80
17 2026-08-24 07:01 639231508078650885
2 ms 124.150.132.80
16 2026-08-24 06:44 639231498210697093
4 ms 124.150.132.80
15 2026-08-24 06:28 639231488109699360
4 ms 124.150.132.80
14 2026-08-24 05:35 639231456772510692
15 ms 124.150.132.80
13 2026-08-24 05:19 639231447084631185
1221 ms 124.150.132.80
12 2026-08-24 05:03 639231437208519473
9 ms 124.150.132.80
11 2026-08-24 04:46 639231427209627490
4 ms 124.150.132.80
10 2026-08-24 03:53 639231395791246644
2 ms 124.150.132.80
9 2026-08-24 03:37 639231386075551458
5 ms 124.150.132.80
8 2026-08-24 03:21 639231376208713791
1215 ms 124.150.132.80
7 2026-08-24 03:05 639231366170589276
1212 ms 124.150.132.80
6 2026-08-24 02:12 639231334732159368
2 ms 124.150.132.80
5 2026-08-24 01:56 639231325035670078
1319 ms 124.150.132.80
4 2026-08-24 01:39 639231315132253837
1226 ms 124.150.132.80
3 2026-08-24 01:23 639231305014280808
3 ms 124.150.132.80
2 2026-08-24 00:30 639231273779380675
2 ms 124.150.132.80
1 2026-08-24 00:14 639231264180839154
3 ms 124.150.132.80