DNS response history for ns1.chuo-yakkyoku.jp

ns1.chuo-yakkyoku.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-24. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 469 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.chuo-yakkyoku.jp.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

469 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.123.7.210

Most recently resolved hosting IP on selected date

Successful Responses

38

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.chuo-yakkyoku.jp

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
38 2026-08-24 15:54 639231828211839931
981 ms 153.123.7.210
37 2026-08-24 15:37 639231818080917481
498 ms 153.123.7.210
36 2026-08-24 15:20 639231807961539652
20 ms 153.123.7.210
35 2026-08-24 15:03 639231797631669865
999 ms 153.123.7.210
34 2026-08-24 14:10 639231765923559455
498 ms 153.123.7.210
33 2026-08-24 13:54 639231755868832964
506 ms 153.123.7.210
32 2026-08-24 13:37 639231745628278877
979 ms 153.123.7.210
31 2026-08-24 13:19 639231735407682062
986 ms 153.123.7.210
30 2026-08-24 12:27 639231703815441688
992 ms 153.123.7.210
29 2026-08-24 12:10 639231693747052549
493 ms 153.123.7.210
28 2026-08-24 11:53 639231683712487276
3 ms 153.123.7.210
27 2026-08-24 11:36 639231673513573868
3 ms 153.123.7.210
26 2026-08-24 10:43 639231641791249939
488 ms 153.123.7.210
25 2026-08-24 10:27 639231631866211033
501 ms 153.123.7.210
24 2026-08-24 10:10 639231621644955316
996 ms 153.123.7.210
23 2026-08-24 09:53 639231611478799259
751 ms 153.123.7.210
22 2026-08-24 09:00 639231579923718211
493 ms 153.123.7.210
21 2026-08-24 08:44 639231569810702936
679 ms 153.123.7.210
20 2026-08-24 08:27 639231559762411619
6 ms 153.123.7.210
19 2026-08-24 08:10 639231549663595407
3 ms 153.123.7.210
18 2026-08-24 07:17 639231518076817246
4 ms 153.123.7.210
17 2026-08-24 07:01 639231508078650885
3 ms 153.123.7.210
16 2026-08-24 06:44 639231498210697093
573 ms 153.123.7.210
15 2026-08-24 06:27 639231488109699360
766 ms 153.123.7.210
14 2026-08-24 05:35 639231456772510692
742 ms 153.123.7.210
13 2026-08-24 05:19 639231447084631185
492 ms 153.123.7.210
12 2026-08-24 05:02 639231437208519473
988 ms 153.123.7.210
11 2026-08-24 04:46 639231427209627490
2 ms 153.123.7.210
10 2026-08-24 03:53 639231395791246644
3 ms 153.123.7.210
9 2026-08-24 03:37 639231386075551458
483 ms 153.123.7.210
8 2026-08-24 03:21 639231376208713791
3 ms 153.123.7.210
7 2026-08-24 03:04 639231366170589276
2 ms 153.123.7.210
6 2026-08-24 02:12 639231334732159368
508 ms 153.123.7.210
5 2026-08-24 01:55 639231325035670078
786 ms 153.123.7.210
4 2026-08-24 01:39 639231315132253837
525 ms 153.123.7.210
3 2026-08-24 01:22 639231305014280808
1041 ms 153.123.7.210
2 2026-08-24 00:30 639231273779380675
4 ms 153.123.7.210
1 2026-08-24 00:14 639231264180839154
12 ms 153.123.7.210