DNS response history for ns02.oreilly.tw

ns02.oreilly.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 33 DNS check records, 33 successful responses, 0 failed responses, and 464 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 ns02.oreilly.tw.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

464 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.130.141.77

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns02.oreilly.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
33 2026-08-24 13:53 639231755868832964
596 ms 220.130.141.77
32 2026-08-24 13:36 639231745628278877
594 ms 220.130.141.77
31 2026-08-24 13:19 639231735407682062
580 ms 220.130.141.77
30 2026-08-24 12:26 639231703815441688
570 ms 220.130.141.77
29 2026-08-24 12:10 639231693747052549
595 ms 220.130.141.77
28 2026-08-24 11:53 639231683712487276
867 ms 220.130.141.77
27 2026-08-24 11:36 639231673513573868
748 ms 220.130.141.77
26 2026-08-24 10:43 639231641791249939
598 ms 220.130.141.77
25 2026-08-24 10:26 639231631866211033
607 ms 220.130.141.77
24 2026-08-24 10:10 639231621644955316
590 ms 220.130.141.77
23 2026-08-24 09:52 639231611478799259
587 ms 220.130.141.77
22 2026-08-24 09:00 639231579923718211
584 ms 220.130.141.77
21 2026-08-24 08:43 639231569810702936
584 ms 220.130.141.77
20 2026-08-24 08:26 639231559762411619
594 ms 220.130.141.77
19 2026-08-24 08:09 639231549663595407
3 ms 220.130.141.77
18 2026-08-24 07:17 639231518076817246
595 ms 220.130.141.77
17 2026-08-24 07:00 639231508078650885
3 ms 220.130.141.77
16 2026-08-24 06:43 639231498210697093
588 ms 220.130.141.77
15 2026-08-24 06:27 639231488109699360
3 ms 220.130.141.77
14 2026-08-24 05:35 639231456772510692
571 ms 220.130.141.77
13 2026-08-24 05:18 639231447084631185
2254 ms 220.130.141.77
12 2026-08-24 05:02 639231437208519473
3 ms 220.130.141.77
11 2026-08-24 04:45 639231427209627490
575 ms 220.130.141.77
10 2026-08-24 03:53 639231395791246644
264 ms 220.130.141.77
9 2026-08-24 03:37 639231386075551458
3 ms 220.130.141.77
8 2026-08-24 03:20 639231376208713791
583 ms 220.130.141.77
7 2026-08-24 03:04 639231366170589276
2 ms 220.130.141.77
6 2026-08-24 02:11 639231334732159368
3 ms 220.130.141.77
5 2026-08-24 01:55 639231325035670078
583 ms 220.130.141.77
4 2026-08-24 01:38 639231315132253837
3 ms 220.130.141.77
3 2026-08-24 01:22 639231305014280808
3 ms 220.130.141.77
2 2026-08-24 00:29 639231273779380675
4 ms 220.130.141.77
1 2026-08-24 00:13 639231264180839154
576 ms 220.130.141.77