DNS response history for dns2.liangyu.com.tw

dns2.liangyu.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 465 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 dns2.liangyu.com.tw.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

465 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.65.107.182

Most recently resolved hosting IP on selected date

Successful Responses

35

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 dns2.liangyu.com.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
35 2026-08-26 11:39 639233403515141099
699 ms 210.65.107.182
34 2026-08-26 10:45 639233370841350248
286 ms 210.65.107.182
33 2026-08-26 10:27 639233360361507238
298 ms 210.65.107.182
32 2026-08-26 10:10 639233350067824371
282 ms 210.65.107.182
31 2026-08-26 09:53 639233339545274518
5 ms 210.65.107.182
30 2026-08-26 09:35 639233329214918079
280 ms 210.65.107.182
29 2026-08-26 09:18 639233318749762337
3 ms 210.65.107.182
28 2026-08-26 09:01 639233308387917838
3 ms 210.65.107.182
27 2026-08-26 08:43 639233297961740122
711 ms 210.65.107.182
26 2026-08-26 08:26 639233287487159094
591 ms 210.65.107.182
25 2026-08-26 08:09 639233276995531707
282 ms 210.65.107.182
24 2026-08-26 07:51 639233266521568229
804 ms 210.65.107.182
23 2026-08-26 07:33 639233256081047431
285 ms 210.65.107.182
22 2026-08-26 06:39 639233223620132921
293 ms 210.65.107.182
21 2026-08-26 06:22 639233213287814244
682 ms 210.65.107.182
20 2026-08-26 06:05 639233202925983161
568 ms 210.65.107.182
19 2026-08-26 05:48 639233192644780696
730 ms 210.65.107.182
18 2026-08-26 05:30 639233182401183833
566 ms 210.65.107.182
17 2026-08-26 05:13 639233172074181051
284 ms 210.65.107.182
16 2026-08-26 04:56 639233161808421455
564 ms 210.65.107.182
15 2026-08-26 04:39 639233151357344052
693 ms 210.65.107.182
14 2026-08-26 04:22 639233141034116946
700 ms 210.65.107.182
13 2026-08-26 04:05 639233130828334142
575 ms 210.65.107.182
12 2026-08-26 03:47 639233120373450007
698 ms 210.65.107.182
11 2026-08-26 03:30 639233110066216193
691 ms 210.65.107.182
10 2026-08-26 02:37 639233078065410564
600 ms 210.65.107.182
9 2026-08-26 02:20 639233067787457832
571 ms 210.65.107.182
8 2026-08-26 02:02 639233057501801162
557 ms 210.65.107.182
7 2026-08-26 01:45 639233047089431703
3 ms 210.65.107.182
6 2026-08-26 01:28 639233036754790688
728 ms 210.65.107.182
5 2026-08-26 01:11 639233026412602472
3 ms 210.65.107.182
4 2026-08-26 00:53 639233016064066127
689 ms 210.65.107.182
3 2026-08-26 00:36 639233005922655772
685 ms 210.65.107.182
2 2026-08-26 00:19 639232995672256907
303 ms 210.65.107.182
1 2026-08-26 00:02 639232985300872416
572 ms 210.65.107.182