DNS response history for dns.yaoder.com.tw

dns.yaoder.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 32 DNS check records, 32 successful responses, 0 failed responses, and 344 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 dns.yaoder.com.tw.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

344 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.23.144.155

Most recently resolved hosting IP on selected date

Successful Responses

32

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 dns.yaoder.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
32 2026-08-24 13:36 639231745628278877
3 ms 211.23.144.155
31 2026-08-24 13:19 639231735407682062
699 ms 211.23.144.155
30 2026-08-24 12:26 639231703815441688
292 ms 211.23.144.155
29 2026-08-24 12:10 639231693747052549
1105 ms 211.23.144.155
28 2026-08-24 11:53 639231683712487276
599 ms 211.23.144.155
27 2026-08-24 11:36 639231673513573868
592 ms 211.23.144.155
26 2026-08-24 10:43 639231641791249939
592 ms 211.23.144.155
25 2026-08-24 10:26 639231631866211033
596 ms 211.23.144.155
24 2026-08-24 10:10 639231621644955316
578 ms 211.23.144.155
23 2026-08-24 09:53 639231611478799259
586 ms 211.23.144.155
22 2026-08-24 09:00 639231579923718211
577 ms 211.23.144.155
21 2026-08-24 08:43 639231569810702936
300 ms 211.23.144.155
20 2026-08-24 08:26 639231559762411619
12 ms 211.23.144.155
19 2026-08-24 08:09 639231549663595407
605 ms 211.23.144.155
18 2026-08-24 07:17 639231518076817246
17 ms 211.23.144.155
17 2026-08-24 07:00 639231508078650885
282 ms 211.23.144.155
16 2026-08-24 06:44 639231498210697093
589 ms 211.23.144.155
15 2026-08-24 06:27 639231488109699360
2 ms 211.23.144.155
14 2026-08-24 05:35 639231456772510692
253 ms 211.23.144.155
13 2026-08-24 05:18 639231447084631185
3 ms 211.23.144.155
12 2026-08-24 05:02 639231437208519473
304 ms 211.23.144.155
11 2026-08-24 04:45 639231427209627490
4 ms 211.23.144.155
10 2026-08-24 03:53 639231395791246644
587 ms 211.23.144.155
9 2026-08-24 03:37 639231386075551458
595 ms 211.23.144.155
8 2026-08-24 03:20 639231376208713791
2 ms 211.23.144.155
7 2026-08-24 03:04 639231366170589276
2 ms 211.23.144.155
6 2026-08-24 02:11 639231334732159368
3 ms 211.23.144.155
5 2026-08-24 01:55 639231325035670078
2 ms 211.23.144.155
4 2026-08-24 01:39 639231315132253837
5 ms 211.23.144.155
3 2026-08-24 01:22 639231305014280808
2 ms 211.23.144.155
2 2026-08-24 00:29 639231273779380675
616 ms 211.23.144.155
1 2026-08-24 00:13 639231264180839154
602 ms 211.23.144.155