DNS response history for ns.rlco.co.jp

ns.rlco.co.jp 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 566 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.rlco.co.jp.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

566 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

153.123.7.98

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.rlco.co.jp

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
525 ms 153.123.7.98
26 2026-08-26 08:27 639233287487159094
1001 ms 153.123.7.98
25 2026-08-26 08:09 639233276995531707
1016 ms 153.123.7.98
24 2026-08-26 07:52 639233266521568229
506 ms 153.123.7.98
23 2026-08-26 07:34 639233256081047431
997 ms 153.123.7.98
22 2026-08-26 06:40 639233223620132921
512 ms 153.123.7.98
21 2026-08-26 06:23 639233213287814244
548 ms 153.123.7.98
20 2026-08-26 06:06 639233202925983161
774 ms 153.123.7.98
19 2026-08-26 05:48 639233192644780696
520 ms 153.123.7.98
18 2026-08-26 05:31 639233182401183833
984 ms 153.123.7.98
17 2026-08-26 05:14 639233172074181051
506 ms 153.123.7.98
16 2026-08-26 04:57 639233161808421455
1016 ms 153.123.7.98
15 2026-08-26 04:40 639233151357344052
3 ms 153.123.7.98
14 2026-08-26 04:22 639233141034116946
1069 ms 153.123.7.98
13 2026-08-26 04:05 639233130828334142
2 ms 153.123.7.98
12 2026-08-26 03:48 639233120373450007
504 ms 153.123.7.98
11 2026-08-26 03:31 639233110066216193
1235 ms 153.123.7.98
10 2026-08-26 02:37 639233078065410564
519 ms 153.123.7.98
9 2026-08-26 02:20 639233067787457832
3 ms 153.123.7.98
8 2026-08-26 02:03 639233057501801162
491 ms 153.123.7.98
7 2026-08-26 01:46 639233047089431703
504 ms 153.123.7.98
6 2026-08-26 01:29 639233036754790688
2 ms 153.123.7.98
5 2026-08-26 01:11 639233026412602472
3 ms 153.123.7.98
4 2026-08-26 00:54 639233016064066127
506 ms 153.123.7.98
3 2026-08-26 00:37 639233005922655772
496 ms 153.123.7.98
2 2026-08-26 00:20 639232995672256907
506 ms 153.123.7.98
1 2026-08-26 00:03 639232985300872416
521 ms 153.123.7.98