DNS response history for ad2.sanyofund.org.tw

ad2.sanyofund.org.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 518 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 ad2.sanyofund.org.tw.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

518 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.63.212.145

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ad2.sanyofund.org.tw

Showing DNS history for 2026-08-26 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
36 2026-08-26 11:57 639233414056832719
4 ms 210.63.212.145
35 2026-08-26 11:40 639233403515141099
514 ms 210.63.212.145
34 2026-08-26 10:45 639233370841350248
4 ms 210.63.212.145
33 2026-08-26 10:28 639233360361507238
650 ms 210.63.212.145
32 2026-08-26 10:10 639233350067824371
523 ms 210.63.212.145
31 2026-08-26 09:53 639233339545274518
518 ms 210.63.212.145
30 2026-08-26 09:36 639233329214918079
520 ms 210.63.212.145
29 2026-08-26 09:19 639233318749762337
518 ms 210.63.212.145
28 2026-08-26 09:01 639233308387917838
3 ms 210.63.212.145
27 2026-08-26 08:44 639233297961740122
528 ms 210.63.212.145
26 2026-08-26 08:26 639233287487159094
520 ms 210.63.212.145
25 2026-08-26 08:09 639233276995531707
670 ms 210.63.212.145
24 2026-08-26 07:51 639233266521568229
896 ms 210.63.212.145
23 2026-08-26 07:34 639233256081047431
540 ms 210.63.212.145
22 2026-08-26 06:40 639233223620132921
604 ms 210.63.212.145
21 2026-08-26 06:23 639233213287814244
3 ms 210.63.212.145
20 2026-08-26 06:05 639233202925983161
632 ms 210.63.212.145
19 2026-08-26 05:48 639233192644780696
536 ms 210.63.212.145
18 2026-08-26 05:31 639233182401183833
529 ms 210.63.212.145
17 2026-08-26 05:14 639233172074181051
879 ms 210.63.212.145
16 2026-08-26 04:57 639233161808421455
3 ms 210.63.212.145
15 2026-08-26 04:39 639233151357344052
2 ms 210.63.212.145
14 2026-08-26 04:22 639233141034116946
519 ms 210.63.212.145
13 2026-08-26 04:05 639233130828334142
512 ms 210.63.212.145
12 2026-08-26 03:48 639233120373450007
678 ms 210.63.212.145
11 2026-08-26 03:30 639233110066216193
2511 ms 210.63.212.145
10 2026-08-26 02:37 639233078065410564
2 ms 210.63.212.145
9 2026-08-26 02:20 639233067787457832
506 ms 210.63.212.145
8 2026-08-26 02:03 639233057501801162
511 ms 210.63.212.145
7 2026-08-26 01:46 639233047089431703
520 ms 210.63.212.145
6 2026-08-26 01:28 639233036754790688
2 ms 210.63.212.145
5 2026-08-26 01:11 639233026412602472
648 ms 210.63.212.145
4 2026-08-26 00:54 639233016064066127
508 ms 210.63.212.145
3 2026-08-26 00:37 639233005922655772
647 ms 210.63.212.145
2 2026-08-26 00:20 639232995672256907
503 ms 210.63.212.145
1 2026-08-26 00:03 639232985300872416
981 ms 210.63.212.145