DNS response history for ns03.arakawachem.co.jp

ns03.arakawachem.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-24. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 591 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 ns03.arakawachem.co.jp.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

591 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.248.5.5

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 ns03.arakawachem.co.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
27 2026-08-24 11:36 639231673513573868
532 ms 202.248.5.5
26 2026-08-24 10:43 639231641791249939
513 ms 202.248.5.5
25 2026-08-24 10:27 639231631866211033
524 ms 202.248.5.5
24 2026-08-24 10:10 639231621644955316
523 ms 202.248.5.5
23 2026-08-24 09:53 639231611478799259
535 ms 202.248.5.5
22 2026-08-24 09:00 639231579923718211
556 ms 202.248.5.5
21 2026-08-24 08:44 639231569810702936
332 ms 202.248.5.5
20 2026-08-24 08:26 639231559762411619
682 ms 202.248.5.5
19 2026-08-24 08:10 639231549663595407
563 ms 202.248.5.5
18 2026-08-24 07:17 639231518076817246
508 ms 202.248.5.5
17 2026-08-24 07:01 639231508078650885
516 ms 202.248.5.5
16 2026-08-24 06:44 639231498210697093
769 ms 202.248.5.5
15 2026-08-24 06:27 639231488109699360
516 ms 202.248.5.5
14 2026-08-24 05:35 639231456772510692
565 ms 202.248.5.5
13 2026-08-24 05:18 639231447084631185
525 ms 202.248.5.5
12 2026-08-24 05:02 639231437208519473
271 ms 202.248.5.5
11 2026-08-24 04:46 639231427209627490
516 ms 202.248.5.5
10 2026-08-24 03:53 639231395791246644
537 ms 202.248.5.5
9 2026-08-24 03:37 639231386075551458
527 ms 202.248.5.5
8 2026-08-24 03:21 639231376208713791
511 ms 202.248.5.5
7 2026-08-24 03:04 639231366170589276
561 ms 202.248.5.5
6 2026-08-24 02:12 639231334732159368
519 ms 202.248.5.5
5 2026-08-24 01:55 639231325035670078
2522 ms 202.248.5.5
4 2026-08-24 01:39 639231315132253837
291 ms 202.248.5.5
3 2026-08-24 01:22 639231305014280808
513 ms 202.248.5.5
2 2026-08-24 00:30 639231273779380675
541 ms 202.248.5.5
1 2026-08-24 00:14 639231264180839154
497 ms 202.248.5.5