DNS response history for ns2.webhan.com.tw

ns2.webhan.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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 600 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 ns2.webhan.com.tw.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

600 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.130.11.93

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns2.webhan.com.tw

Showing DNS history for 2026-08-25 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
37 2026-08-25 12:42 639232576780683689
571 ms 220.130.11.93
36 2026-08-25 12:24 639232566381512620
589 ms 220.130.11.93
35 2026-08-25 12:07 639232556111768563
762 ms 220.130.11.93
34 2026-08-25 11:50 639232545839529039
732 ms 220.130.11.93
33 2026-08-25 11:33 639232535349285207
591 ms 220.130.11.93
32 2026-08-25 11:15 639232524938080723
595 ms 220.130.11.93
31 2026-08-25 10:22 639232492740373468
588 ms 220.130.11.93
30 2026-08-25 10:04 639232482235303141
578 ms 220.130.11.93
29 2026-08-25 09:47 639232471861770303
744 ms 220.130.11.93
28 2026-08-25 09:30 639232461630217327
597 ms 220.130.11.93
27 2026-08-25 09:12 639232451282965990
726 ms 220.130.11.93
26 2026-08-25 08:55 639232440814614938
748 ms 220.130.11.93
25 2026-08-25 08:38 639232430410720425
705 ms 220.130.11.93
24 2026-08-25 08:20 639232420003096185
3 ms 220.130.11.93
23 2026-08-25 08:03 639232409467287444
3 ms 220.130.11.93
22 2026-08-25 07:46 639232399077195997
1255 ms 220.130.11.93
21 2026-08-25 07:28 639232388731528337
583 ms 220.130.11.93
20 2026-08-25 07:11 639232378288598612
1021 ms 220.130.11.93
19 2026-08-25 06:17 639232346196373643
592 ms 220.130.11.93
18 2026-08-25 06:00 639232336112370741
771 ms 220.130.11.93
17 2026-08-25 05:44 639232326146508970
577 ms 220.130.11.93
16 2026-08-25 05:27 639232316189381720
583 ms 220.130.11.93
15 2026-08-25 05:10 639232306217998913
2 ms 220.130.11.93
14 2026-08-25 04:54 639232296255744174
585 ms 220.130.11.93
13 2026-08-25 04:37 639232286095760789
592 ms 220.130.11.93
12 2026-08-25 04:20 639232276086186273
759 ms 220.130.11.93
11 2026-08-25 04:03 639232265900986425
588 ms 220.130.11.93
10 2026-08-25 03:46 639232255723518075
598 ms 220.130.11.93
9 2026-08-25 03:29 639232245484452890
594 ms 220.130.11.93
8 2026-08-25 03:12 639232235157175331
745 ms 220.130.11.93
7 2026-08-25 02:19 639232203197189095
583 ms 220.130.11.93
6 2026-08-25 02:02 639232192844564298
790 ms 220.130.11.93
5 2026-08-25 01:45 639232182496008942
588 ms 220.130.11.93
4 2026-08-25 01:27 639232172197053132
694 ms 220.130.11.93
3 2026-08-25 00:34 639232140250307418
583 ms 220.130.11.93
2 2026-08-25 00:17 639232129927860324
2 ms 220.130.11.93
1 2026-08-25 00:00 639232119551972438
584 ms 220.130.11.93