DNS response history for dns2.cpc.com.tw

dns2.cpc.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 33 DNS check records, 33 successful responses, 0 failed responses, and 701 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.cpc.com.tw.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

701 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.39.184.66

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 dns2.cpc.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
33 2026-08-26 10:28 639233360361507238
594 ms 202.39.184.66
32 2026-08-26 10:10 639233350067824371
686 ms 202.39.184.66
31 2026-08-26 09:53 639233339545274518
631 ms 202.39.184.66
30 2026-08-26 09:36 639233329214918079
712 ms 202.39.184.66
29 2026-08-26 09:19 639233318749762337
590 ms 202.39.184.66
28 2026-08-26 09:01 639233308387917838
599 ms 202.39.184.66
27 2026-08-26 08:44 639233297961740122
710 ms 202.39.184.66
26 2026-08-26 08:26 639233287487159094
822 ms 202.39.184.66
25 2026-08-26 08:09 639233276995531707
590 ms 202.39.184.66
24 2026-08-26 07:51 639233266521568229
834 ms 202.39.184.66
23 2026-08-26 07:34 639233256081047431
606 ms 202.39.184.66
22 2026-08-26 06:40 639233223620132921
710 ms 202.39.184.66
21 2026-08-26 06:23 639233213287814244
711 ms 202.39.184.66
20 2026-08-26 06:05 639233202925983161
622 ms 202.39.184.66
19 2026-08-26 05:48 639233192644780696
758 ms 202.39.184.66
18 2026-08-26 05:31 639233182401183833
587 ms 202.39.184.66
17 2026-08-26 05:14 639233172074181051
874 ms 202.39.184.66
16 2026-08-26 04:57 639233161808421455
747 ms 202.39.184.66
15 2026-08-26 04:40 639233151357344052
693 ms 202.39.184.66
14 2026-08-26 04:22 639233141034116946
719 ms 202.39.184.66
13 2026-08-26 04:05 639233130828334142
581 ms 202.39.184.66
12 2026-08-26 03:48 639233120373450007
581 ms 202.39.184.66
11 2026-08-26 03:30 639233110066216193
597 ms 202.39.184.66
10 2026-08-26 02:37 639233078065410564
928 ms 202.39.184.66
9 2026-08-26 02:20 639233067787457832
1045 ms 202.39.184.66
8 2026-08-26 02:03 639233057501801162
571 ms 202.39.184.66
7 2026-08-26 01:46 639233047089431703
781 ms 202.39.184.66
6 2026-08-26 01:28 639233036754790688
751 ms 202.39.184.66
5 2026-08-26 01:11 639233026412602472
767 ms 202.39.184.66
4 2026-08-26 00:54 639233016064066127
717 ms 202.39.184.66
3 2026-08-26 00:37 639233005922655772
588 ms 202.39.184.66
2 2026-08-26 00:20 639232995672256907
807 ms 202.39.184.66
1 2026-08-26 00:03 639232985300872416
624 ms 202.39.184.66