DNS response history for dns2.i-lan.com.tw

dns2.i-lan.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 34 DNS check records, 33 successful responses, 1 failed responses, and 1141 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.i-lan.com.tw.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

1141 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.130.43.120

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for dns2.i-lan.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
34 2026-08-26 10:46 639233370841350248
569 ms 220.130.43.120
33 2026-08-26 10:29 639233360361507238
827 ms 220.130.43.120
32 2026-08-26 10:12 639233350067824371
1661 ms 220.130.43.120
31 2026-08-26 09:54 639233339545274518
585 ms 220.130.43.120
30 2026-08-26 09:37 639233329214918079
2008 ms 220.130.43.120
29 2026-08-26 09:20 639233318749762337
674 ms 220.130.43.120
28 2026-08-26 09:02 639233308387917838
2566 ms 220.130.43.120
27 2026-08-26 08:45 639233297961740122
873 ms 220.130.43.120
26 2026-08-26 08:28 639233287487159094
754 ms 220.130.43.120
25 2026-08-26 08:10 639233276995531707
1024 ms 220.130.43.120
24 2026-08-26 07:53 639233266521568229
1432 ms 220.130.43.120
23 2026-08-26 07:35 639233256081047431
1828 ms 220.130.43.120
22 2026-08-26 06:41 639233223620132921
580 ms 220.130.43.120
21 2026-08-26 06:24 639233213287814244
755 ms 220.130.43.120
20 2026-08-26 06:06 639233202925983161
569 ms 220.130.43.120
19 2026-08-26 05:49 639233192644780696
697 ms 220.130.43.120
18 2026-08-26 05:32 639233182401183833
591 ms 220.130.43.120
17 2026-08-26 05:15 639233172074181051
1361 ms 220.130.43.120
16 2026-08-26 04:58 639233161808421455
1369 ms 220.130.43.120
15 2026-08-26 04:41 639233151357344052
567 ms 220.130.43.120
14 2026-08-26 04:23 639233141034116946
577 ms 220.130.43.120
13 2026-08-26 04:06 639233130828334142
603 ms 220.130.43.120
12 2026-08-26 03:49 639233120373450007
1167 ms 220.130.43.120
11 2026-08-26 03:32 639233110066216193
593 ms 220.130.43.120
10 2026-08-26 02:38 639233078065410564
3654 ms 220.130.43.120
9 2026-08-26 02:21 639233067787457832
1033 ms 220.130.43.120
8 2026-08-26 02:04 639233057501801162
607 ms 220.130.43.120
7 2026-08-26 01:47 639233047089431703
580 ms 220.130.43.120
6 2026-08-26 01:30 639233036754790688
-
5 2026-08-26 01:12 639233026412602472
3833 ms 220.130.43.120
4 2026-08-26 00:55 639233016064066127
838 ms 220.130.43.120
3 2026-08-26 00:38 639233005922655772
795 ms 220.130.43.120
2 2026-08-26 00:21 639232995672256907
772 ms 220.130.43.120
1 2026-08-26 00:04 639232985300872416
1301 ms 220.130.43.120