DNS response history for ns02.omicard.com.tw

ns02.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 466 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 ns02.omicard.com.tw.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

466 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

113.196.228.14

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns02.omicard.com.tw

Showing DNS history for 2026-08-24 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
30 2026-08-24 12:26 639231703815441688
492 ms 113.196.228.14
29 2026-08-24 12:09 639231693747052549
768 ms 113.196.228.14
28 2026-08-24 11:52 639231683712487276
251 ms 113.196.228.14
27 2026-08-24 11:35 639231673513573868
254 ms 113.196.228.14
26 2026-08-24 10:42 639231641791249939
5 ms 113.196.228.14
25 2026-08-24 10:26 639231631866211033
3 ms 113.196.228.14
24 2026-08-24 10:09 639231621644955316
213 ms 113.196.228.14
23 2026-08-24 09:52 639231611478799259
504 ms 113.196.228.14
22 2026-08-24 08:59 639231579923718211
491 ms 113.196.228.14
21 2026-08-24 08:43 639231569810702936
245 ms 113.196.228.14
20 2026-08-24 08:26 639231559762411619
504 ms 113.196.228.14
19 2026-08-24 08:09 639231549663595407
248 ms 113.196.228.14
18 2026-08-24 07:16 639231518076817246
27 ms 113.196.228.14
17 2026-08-24 07:00 639231508078650885
1226 ms 113.196.228.14
16 2026-08-24 06:43 639231498210697093
507 ms 113.196.228.14
15 2026-08-24 06:26 639231488109699360
497 ms 113.196.228.14
14 2026-08-24 05:34 639231456772510692
678 ms 113.196.228.14
13 2026-08-24 05:18 639231447084631185
3 ms 113.196.228.14
12 2026-08-24 05:01 639231437208519473
504 ms 113.196.228.14
11 2026-08-24 04:45 639231427209627490
245 ms 113.196.228.14
10 2026-08-24 03:52 639231395791246644
519 ms 113.196.228.14
9 2026-08-24 03:36 639231386075551458
499 ms 113.196.228.14
8 2026-08-24 03:20 639231376208713791
499 ms 113.196.228.14
7 2026-08-24 03:03 639231366170589276
282 ms 113.196.228.14
6 2026-08-24 02:11 639231334732159368
3 ms 113.196.228.14
5 2026-08-24 01:54 639231325035670078
1019 ms 113.196.228.14
4 2026-08-24 01:38 639231315132253837
617 ms 113.196.228.14
3 2026-08-24 01:21 639231305014280808
181 ms 113.196.228.14
2 2026-08-24 00:29 639231273779380675
2188 ms 113.196.228.14
1 2026-08-24 00:13 639231264180839154
493 ms 113.196.228.14