DNS response history for ns2.popo.tw

ns2.popo.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 33 DNS check records, 33 successful responses, 0 failed responses, and 503 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.popo.tw.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

503 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.105.200.85

Most recently resolved hosting IP on selected date

Successful Responses

33

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.popo.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
33 2026-08-25 11:33 639232535349285207
304 ms 27.105.200.85
32 2026-08-25 11:15 639232524938080723
610 ms 27.105.200.85
31 2026-08-25 10:21 639232492740373468
604 ms 27.105.200.85
30 2026-08-25 10:04 639232482235303141
322 ms 27.105.200.85
29 2026-08-25 09:47 639232471861770303
606 ms 27.105.200.85
28 2026-08-25 09:30 639232461630217327
589 ms 27.105.200.85
27 2026-08-25 09:12 639232451282965990
739 ms 27.105.200.85
26 2026-08-25 08:55 639232440814614938
743 ms 27.105.200.85
25 2026-08-25 08:38 639232430410720425
607 ms 27.105.200.85
24 2026-08-25 08:20 639232420003096185
605 ms 27.105.200.85
23 2026-08-25 08:03 639232409467287444
606 ms 27.105.200.85
22 2026-08-25 07:46 639232399077195997
8 ms 27.105.200.85
21 2026-08-25 07:28 639232388731528337
602 ms 27.105.200.85
20 2026-08-25 07:11 639232378288598612
601 ms 27.105.200.85
19 2026-08-25 06:17 639232346196373643
595 ms 27.105.200.85
18 2026-08-25 06:00 639232336112370741
592 ms 27.105.200.85
17 2026-08-25 05:44 639232326146508970
582 ms 27.105.200.85
16 2026-08-25 05:27 639232316189381720
239 ms 27.105.200.85
15 2026-08-25 05:10 639232306217998913
294 ms 27.105.200.85
14 2026-08-25 04:54 639232296255744174
299 ms 27.105.200.85
13 2026-08-25 04:37 639232286095760789
612 ms 27.105.200.85
12 2026-08-25 04:20 639232276086186273
615 ms 27.105.200.85
11 2026-08-25 04:03 639232265900986425
591 ms 27.105.200.85
10 2026-08-25 03:46 639232255723518075
293 ms 27.105.200.85
9 2026-08-25 03:29 639232245484452890
314 ms 27.105.200.85
8 2026-08-25 03:12 639232235157175331
302 ms 27.105.200.85
7 2026-08-25 02:19 639232203197189095
600 ms 27.105.200.85
6 2026-08-25 02:02 639232192844564298
731 ms 27.105.200.85
5 2026-08-25 01:45 639232182496008942
616 ms 27.105.200.85
4 2026-08-25 01:27 639232172197053132
600 ms 27.105.200.85
3 2026-08-25 00:34 639232140250307418
294 ms 27.105.200.85
2 2026-08-25 00:17 639232129927860324
295 ms 27.105.200.85
1 2026-08-25 00:00 639232119551972438
603 ms 27.105.200.85