DNS response history for ns01.omicard.com.tw

ns01.omicard.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 35 DNS check records, 35 successful responses, 0 failed responses, and 565 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 ns01.omicard.com.tw.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

565 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

113.196.228.4

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns01.omicard.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
35 2026-08-26 11:39 639233403515141099
516 ms 113.196.228.4
34 2026-08-26 10:44 639233370841350248
747 ms 113.196.228.4
33 2026-08-26 10:27 639233360361507238
508 ms 113.196.228.4
32 2026-08-26 10:10 639233350067824371
676 ms 113.196.228.4
31 2026-08-26 09:53 639233339545274518
489 ms 113.196.228.4
30 2026-08-26 09:35 639233329214918079
492 ms 113.196.228.4
29 2026-08-26 09:18 639233318749762337
520 ms 113.196.228.4
28 2026-08-26 09:00 639233308387917838
635 ms 113.196.228.4
27 2026-08-26 08:43 639233297961740122
495 ms 113.196.228.4
26 2026-08-26 08:26 639233287487159094
507 ms 113.196.228.4
25 2026-08-26 08:08 639233276995531707
623 ms 113.196.228.4
24 2026-08-26 07:51 639233266521568229
499 ms 113.196.228.4
23 2026-08-26 07:33 639233256081047431
461 ms 113.196.228.4
22 2026-08-26 06:39 639233223620132921
612 ms 113.196.228.4
21 2026-08-26 06:22 639233213287814244
603 ms 113.196.228.4
20 2026-08-26 06:05 639233202925983161
188 ms 113.196.228.4
19 2026-08-26 05:47 639233192644780696
510 ms 113.196.228.4
18 2026-08-26 05:30 639233182401183833
498 ms 113.196.228.4
17 2026-08-26 05:13 639233172074181051
640 ms 113.196.228.4
16 2026-08-26 04:56 639233161808421455
517 ms 113.196.228.4
15 2026-08-26 04:39 639233151357344052
493 ms 113.196.228.4
14 2026-08-26 04:21 639233141034116946
756 ms 113.196.228.4
13 2026-08-26 04:04 639233130828334142
615 ms 113.196.228.4
12 2026-08-26 03:47 639233120373450007
632 ms 113.196.228.4
11 2026-08-26 03:30 639233110066216193
623 ms 113.196.228.4
10 2026-08-26 02:36 639233078065410564
509 ms 113.196.228.4
9 2026-08-26 02:19 639233067787457832
512 ms 113.196.228.4
8 2026-08-26 02:02 639233057501801162
499 ms 113.196.228.4
7 2026-08-26 01:45 639233047089431703
502 ms 113.196.228.4
6 2026-08-26 01:28 639233036754790688
552 ms 113.196.228.4
5 2026-08-26 01:11 639233026412602472
616 ms 113.196.228.4
4 2026-08-26 00:53 639233016064066127
506 ms 113.196.228.4
3 2026-08-26 00:36 639233005922655772
944 ms 113.196.228.4
2 2026-08-26 00:19 639232995672256907
790 ms 113.196.228.4
1 2026-08-26 00:02 639232985300872416
497 ms 113.196.228.4