DNS response history for ns2.arco.com.tw

ns2.arco.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 34 DNS check records, 34 successful responses, 0 failed responses, and 408 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.arco.com.tw.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.61.165.107

Most recently resolved hosting IP on selected date

Successful Responses

34

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.arco.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
34 2026-08-25 11:50 639232545839529039
289 ms 210.61.165.107
33 2026-08-25 11:33 639232535349285207
289 ms 210.61.165.107
32 2026-08-25 11:16 639232524938080723
3 ms 210.61.165.107
31 2026-08-25 10:22 639232492740373468
780 ms 210.61.165.107
30 2026-08-25 10:05 639232482235303141
741 ms 210.61.165.107
29 2026-08-25 09:47 639232471861770303
585 ms 210.61.165.107
28 2026-08-25 09:30 639232461630217327
294 ms 210.61.165.107
27 2026-08-25 09:13 639232451282965990
3 ms 210.61.165.107
26 2026-08-25 08:55 639232440814614938
753 ms 210.61.165.107
25 2026-08-25 08:38 639232430410720425
605 ms 210.61.165.107
24 2026-08-25 08:21 639232420003096185
571 ms 210.61.165.107
23 2026-08-25 08:03 639232409467287444
299 ms 210.61.165.107
22 2026-08-25 07:46 639232399077195997
304 ms 210.61.165.107
21 2026-08-25 07:28 639232388731528337
744 ms 210.61.165.107
20 2026-08-25 07:11 639232378288598612
281 ms 210.61.165.107
19 2026-08-25 06:17 639232346196373643
3 ms 210.61.165.107
18 2026-08-25 06:01 639232336112370741
287 ms 210.61.165.107
17 2026-08-25 05:44 639232326146508970
293 ms 210.61.165.107
16 2026-08-25 05:27 639232316189381720
6 ms 210.61.165.107
15 2026-08-25 05:11 639232306217998913
3 ms 210.61.165.107
14 2026-08-25 04:54 639232296255744174
564 ms 210.61.165.107
13 2026-08-25 04:37 639232286095760789
595 ms 210.61.165.107
12 2026-08-25 04:20 639232276086186273
588 ms 210.61.165.107
11 2026-08-25 04:04 639232265900986425
573 ms 210.61.165.107
10 2026-08-25 03:47 639232255723518075
285 ms 210.61.165.107
9 2026-08-25 03:30 639232245484452890
583 ms 210.61.165.107
8 2026-08-25 03:13 639232235157175331
282 ms 210.61.165.107
7 2026-08-25 02:19 639232203197189095
595 ms 210.61.165.107
6 2026-08-25 02:02 639232192844564298
592 ms 210.61.165.107
5 2026-08-25 01:45 639232182496008942
573 ms 210.61.165.107
4 2026-08-25 01:28 639232172197053132
3 ms 210.61.165.107
3 2026-08-25 00:34 639232140250307418
603 ms 210.61.165.107
2 2026-08-25 00:17 639232129927860324
620 ms 210.61.165.107
1 2026-08-25 00:00 639232119551972438
297 ms 210.61.165.107