DNS response history for ns1.dc.com.tw

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

34

Historical checks stored for this nameserver on selected date

Average Latency

512 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.244.55.153

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 ns1.dc.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
34 2026-08-26 10:44 639233370841350248
886 ms 210.244.55.153
33 2026-08-26 10:27 639233360361507238
19 ms 210.244.55.153
32 2026-08-26 10:10 639233350067824371
507 ms 210.244.55.153
31 2026-08-26 09:52 639233339545274518
566 ms 210.244.55.153
30 2026-08-26 09:35 639233329214918079
581 ms 210.244.55.153
29 2026-08-26 09:18 639233318749762337
436 ms 210.244.55.153
28 2026-08-26 09:00 639233308387917838
389 ms 210.244.55.153
27 2026-08-26 08:43 639233297961740122
509 ms 210.244.55.153
26 2026-08-26 08:26 639233287487159094
615 ms 210.244.55.153
25 2026-08-26 08:08 639233276995531707
226 ms 210.244.55.153
24 2026-08-26 07:51 639233266521568229
561 ms 210.244.55.153
23 2026-08-26 07:33 639233256081047431
262 ms 210.244.55.153
22 2026-08-26 06:39 639233223620132921
602 ms 210.244.55.153
21 2026-08-26 06:22 639233213287814244
535 ms 210.244.55.153
20 2026-08-26 06:04 639233202925983161
604 ms 210.244.55.153
19 2026-08-26 05:47 639233192644780696
596 ms 210.244.55.153
18 2026-08-26 05:30 639233182401183833
500 ms 210.244.55.153
17 2026-08-26 05:13 639233172074181051
586 ms 210.244.55.153
16 2026-08-26 04:56 639233161808421455
584 ms 210.244.55.153
15 2026-08-26 04:39 639233151357344052
793 ms 210.244.55.153
14 2026-08-26 04:21 639233141034116946
369 ms 210.244.55.153
13 2026-08-26 04:04 639233130828334142
402 ms 210.244.55.153
12 2026-08-26 03:47 639233120373450007
1076 ms 210.244.55.153
11 2026-08-26 03:30 639233110066216193
500 ms 210.244.55.153
10 2026-08-26 02:36 639233078065410564
736 ms 210.244.55.153
9 2026-08-26 02:19 639233067787457832
289 ms 210.244.55.153
8 2026-08-26 02:02 639233057501801162
560 ms 210.244.55.153
7 2026-08-26 01:45 639233047089431703
239 ms 210.244.55.153
6 2026-08-26 01:28 639233036754790688
822 ms 210.244.55.153
5 2026-08-26 01:10 639233026412602472
504 ms 210.244.55.153
4 2026-08-26 00:53 639233016064066127
556 ms 210.244.55.153
3 2026-08-26 00:36 639233005922655772
496 ms 210.244.55.153
2 2026-08-26 00:19 639232995672256907
499 ms 210.244.55.153
1 2026-08-26 00:02 639232985300872416
9 ms 210.244.55.153