DNS response history for d01.apap.jp

d01.apap.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 33 DNS check records, 32 successful responses, 1 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 d01.apap.jp.
Records on Selected Date

33

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-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.216.205.79

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for d01.apap.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
33 2026-08-26 10:27 639233360361507238
476 ms 203.216.205.79
32 2026-08-26 10:10 639233350067824371
467 ms 203.216.205.79
31 2026-08-26 09:53 639233339545274518
479 ms 203.216.205.79
30 2026-08-26 09:35 639233329214918079
474 ms 203.216.205.79
29 2026-08-26 09:18 639233318749762337
296 ms 203.216.205.79
28 2026-08-26 09:01 639233308387917838
476 ms 203.216.205.79
27 2026-08-26 08:43 639233297961740122
492 ms 203.216.205.79
26 2026-08-26 08:26 639233287487159094
483 ms 203.216.205.79
25 2026-08-26 08:09 639233276995531707
488 ms 203.216.205.79
24 2026-08-26 07:51 639233266521568229
479 ms 203.216.205.79
23 2026-08-26 07:33 639233256081047431
492 ms 203.216.205.79
22 2026-08-26 06:39 639233223620132921
480 ms 203.216.205.79
21 2026-08-26 06:22 639233213287814244
490 ms 203.216.205.79
20 2026-08-26 06:05 639233202925983161
-
19 2026-08-26 05:48 639233192644780696
477 ms 203.216.205.79
18 2026-08-26 05:30 639233182401183833
477 ms 203.216.205.79
17 2026-08-26 05:13 639233172074181051
471 ms 203.216.205.79
16 2026-08-26 04:56 639233161808421455
487 ms 203.216.205.79
15 2026-08-26 04:39 639233151357344052
474 ms 203.216.205.79
14 2026-08-26 04:22 639233141034116946
486 ms 203.216.205.79
13 2026-08-26 04:05 639233130828334142
307 ms 203.216.205.79
12 2026-08-26 03:47 639233120373450007
484 ms 203.216.205.79
11 2026-08-26 03:30 639233110066216193
493 ms 203.216.205.79
10 2026-08-26 02:37 639233078065410564
475 ms 203.216.205.79
9 2026-08-26 02:20 639233067787457832
495 ms 203.216.205.79
8 2026-08-26 02:02 639233057501801162
323 ms 203.216.205.79
7 2026-08-26 01:45 639233047089431703
472 ms 203.216.205.79
6 2026-08-26 01:28 639233036754790688
513 ms 203.216.205.79
5 2026-08-26 01:11 639233026412602472
475 ms 203.216.205.79
4 2026-08-26 00:53 639233016064066127
488 ms 203.216.205.79
3 2026-08-26 00:36 639233005922655772
487 ms 203.216.205.79
2 2026-08-26 00:19 639232995672256907
483 ms 203.216.205.79
1 2026-08-26 00:02 639232985300872416
483 ms 203.216.205.79