DNS response history for ns2.baiwan.com.tw

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

38

Historical checks stored for this nameserver on selected date

Average Latency

1235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.220.40.120

Most recently resolved hosting IP on selected date

Successful Responses

38

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.baiwan.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
38 2026-08-24 15:55 639231828211839931
8 ms 61.220.40.120
37 2026-08-24 15:39 639231818080917481
1735 ms 61.220.40.120
36 2026-08-24 15:22 639231807961539652
2 ms 61.220.40.120
35 2026-08-24 15:05 639231797631669865
1764 ms 61.220.40.120
34 2026-08-24 14:11 639231765923559455
5 ms 61.220.40.120
33 2026-08-24 13:55 639231755868832964
1885 ms 61.220.40.120
32 2026-08-24 13:38 639231745628278877
1750 ms 61.220.40.120
31 2026-08-24 13:21 639231735407682062
1742 ms 61.220.40.120
30 2026-08-24 12:28 639231703815441688
6 ms 61.220.40.120
29 2026-08-24 12:11 639231693747052549
1160 ms 61.220.40.120
28 2026-08-24 11:54 639231683712487276
1904 ms 61.220.40.120
27 2026-08-24 11:38 639231673513573868
1746 ms 61.220.40.120
26 2026-08-24 10:44 639231641791249939
4 ms 61.220.40.120
25 2026-08-24 10:28 639231631866211033
1749 ms 61.220.40.120
24 2026-08-24 10:11 639231621644955316
1763 ms 61.220.40.120
23 2026-08-24 09:54 639231611478799259
1885 ms 61.220.40.120
22 2026-08-24 09:01 639231579923718211
1760 ms 61.220.40.120
21 2026-08-24 08:45 639231569810702936
1751 ms 61.220.40.120
20 2026-08-24 08:28 639231559762411619
1749 ms 61.220.40.120
19 2026-08-24 08:11 639231549663595407
1739 ms 61.220.40.120
18 2026-08-24 07:18 639231518076817246
1745 ms 61.220.40.120
17 2026-08-24 07:02 639231508078650885
1745 ms 61.220.40.120
16 2026-08-24 06:45 639231498210697093
5 ms 61.220.40.120
15 2026-08-24 06:29 639231488109699360
1744 ms 61.220.40.120
14 2026-08-24 05:36 639231456772510692
757 ms 61.220.40.120
13 2026-08-24 05:20 639231447084631185
3 ms 61.220.40.120
12 2026-08-24 05:03 639231437208519473
1750 ms 61.220.40.120
11 2026-08-24 04:47 639231427209627490
1749 ms 61.220.40.120
10 2026-08-24 03:54 639231395791246644
306 ms 61.220.40.120
9 2026-08-24 03:38 639231386075551458
2 ms 61.220.40.120
8 2026-08-24 03:22 639231376208713791
1755 ms 61.220.40.120
7 2026-08-24 03:05 639231366170589276
1755 ms 61.220.40.120
6 2026-08-24 02:13 639231334732159368
1760 ms 61.220.40.120
5 2026-08-24 01:56 639231325035670078
1747 ms 61.220.40.120
4 2026-08-24 01:40 639231315132253837
277 ms 61.220.40.120
3 2026-08-24 01:23 639231305014280808
3 ms 61.220.40.120
2 2026-08-24 00:31 639231273779380675
1897 ms 61.220.40.120
1 2026-08-24 00:15 639231264180839154
1836 ms 61.220.40.120