DNS response history for ns.richmore.com.tw

ns.richmore.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 27 DNS check records, 27 successful responses, 0 failed responses, and 597 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 ns.richmore.com.tw.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

597 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

124.150.132.50

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns.richmore.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
27 2026-08-26 08:44 639233297961740122
752 ms 124.150.132.50
26 2026-08-26 08:27 639233287487159094
772 ms 124.150.132.50
25 2026-08-26 08:09 639233276995531707
733 ms 124.150.132.50
24 2026-08-26 07:52 639233266521568229
788 ms 124.150.132.50
23 2026-08-26 07:34 639233256081047431
621 ms 124.150.132.50
22 2026-08-26 06:40 639233223620132921
865 ms 124.150.132.50
21 2026-08-26 06:23 639233213287814244
611 ms 124.150.132.50
20 2026-08-26 06:06 639233202925983161
3 ms 124.150.132.50
19 2026-08-26 05:48 639233192644780696
5 ms 124.150.132.50
18 2026-08-26 05:31 639233182401183833
607 ms 124.150.132.50
17 2026-08-26 05:14 639233172074181051
3 ms 124.150.132.50
16 2026-08-26 04:57 639233161808421455
616 ms 124.150.132.50
15 2026-08-26 04:40 639233151357344052
850 ms 124.150.132.50
14 2026-08-26 04:22 639233141034116946
603 ms 124.150.132.50
13 2026-08-26 04:05 639233130828334142
718 ms 124.150.132.50
12 2026-08-26 03:48 639233120373450007
605 ms 124.150.132.50
11 2026-08-26 03:31 639233110066216193
606 ms 124.150.132.50
10 2026-08-26 02:37 639233078065410564
1597 ms 124.150.132.50
9 2026-08-26 02:20 639233067787457832
739 ms 124.150.132.50
8 2026-08-26 02:03 639233057501801162
13 ms 124.150.132.50
7 2026-08-26 01:46 639233047089431703
711 ms 124.150.132.50
6 2026-08-26 01:29 639233036754790688
614 ms 124.150.132.50
5 2026-08-26 01:11 639233026412602472
4 ms 124.150.132.50
4 2026-08-26 00:54 639233016064066127
603 ms 124.150.132.50
3 2026-08-26 00:37 639233005922655772
591 ms 124.150.132.50
2 2026-08-26 00:20 639232995672256907
748 ms 124.150.132.50
1 2026-08-26 00:03 639232985300872416
742 ms 124.150.132.50