DNS response history for dns2.runlong.com.tw

dns2.runlong.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 626 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.runlong.com.tw.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

626 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

211.72.145.34

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 dns2.runlong.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
610 ms 211.72.145.34
36 2026-08-25 12:25 639232566381512620
737 ms 211.72.145.34
35 2026-08-25 12:07 639232556111768563
771 ms 211.72.145.34
34 2026-08-25 11:50 639232545839529039
310 ms 211.72.145.34
33 2026-08-25 11:33 639232535349285207
627 ms 211.72.145.34
32 2026-08-25 11:15 639232524938080723
608 ms 211.72.145.34
31 2026-08-25 10:22 639232492740373468
1225 ms 211.72.145.34
30 2026-08-25 10:05 639232482235303141
615 ms 211.72.145.34
29 2026-08-25 09:47 639232471861770303
608 ms 211.72.145.34
28 2026-08-25 09:30 639232461630217327
783 ms 211.72.145.34
27 2026-08-25 09:13 639232451282965990
603 ms 211.72.145.34
26 2026-08-25 08:55 639232440814614938
613 ms 211.72.145.34
25 2026-08-25 08:38 639232430410720425
608 ms 211.72.145.34
24 2026-08-25 08:21 639232420003096185
609 ms 211.72.145.34
23 2026-08-25 08:03 639232409467287444
612 ms 211.72.145.34
22 2026-08-25 07:46 639232399077195997
757 ms 211.72.145.34
21 2026-08-25 07:28 639232388731528337
634 ms 211.72.145.34
20 2026-08-25 07:11 639232378288598612
635 ms 211.72.145.34
19 2026-08-25 06:17 639232346196373643
647 ms 211.72.145.34
18 2026-08-25 06:00 639232336112370741
612 ms 211.72.145.34
17 2026-08-25 05:44 639232326146508970
620 ms 211.72.145.34
16 2026-08-25 05:27 639232316189381720
596 ms 211.72.145.34
15 2026-08-25 05:11 639232306217998913
589 ms 211.72.145.34
14 2026-08-25 04:54 639232296255744174
621 ms 211.72.145.34
13 2026-08-25 04:37 639232286095760789
263 ms 211.72.145.34
12 2026-08-25 04:20 639232276086186273
616 ms 211.72.145.34
11 2026-08-25 04:04 639232265900986425
571 ms 211.72.145.34
10 2026-08-25 03:47 639232255723518075
595 ms 211.72.145.34
9 2026-08-25 03:30 639232245484452890
611 ms 211.72.145.34
8 2026-08-25 03:13 639232235157175331
756 ms 211.72.145.34
7 2026-08-25 02:19 639232203197189095
600 ms 211.72.145.34
6 2026-08-25 02:02 639232192844564298
242 ms 211.72.145.34
5 2026-08-25 01:45 639232182496008942
614 ms 211.72.145.34
4 2026-08-25 01:27 639232172197053132
798 ms 211.72.145.34
3 2026-08-25 00:34 639232140250307418
611 ms 211.72.145.34
2 2026-08-25 00:17 639232129927860324
609 ms 211.72.145.34
1 2026-08-25 00:00 639232119551972438
634 ms 211.72.145.34