DNS response history for ns2.adpark.ne.jp

ns2.adpark.ne.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 30 DNS check records, 30 successful responses, 0 failed responses, and 651 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 ns2.adpark.ne.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

651 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

175.111.82.53

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns2.adpark.ne.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
30 2026-08-24 12:26 639231703815441688
569 ms 175.111.82.53
29 2026-08-24 12:10 639231693747052549
575 ms 175.111.82.53
28 2026-08-24 11:53 639231683712487276
601 ms 175.111.82.53
27 2026-08-24 11:36 639231673513573868
556 ms 175.111.82.53
26 2026-08-24 10:43 639231641791249939
274 ms 175.111.82.53
25 2026-08-24 10:27 639231631866211033
279 ms 175.111.82.53
24 2026-08-24 10:10 639231621644955316
569 ms 175.111.82.53
23 2026-08-24 09:53 639231611478799259
577 ms 175.111.82.53
22 2026-08-24 09:00 639231579923718211
552 ms 175.111.82.53
21 2026-08-24 08:43 639231569810702936
280 ms 175.111.82.53
20 2026-08-24 08:26 639231559762411619
575 ms 175.111.82.53
19 2026-08-24 08:10 639231549663595407
603 ms 175.111.82.53
18 2026-08-24 07:17 639231518076817246
577 ms 175.111.82.53
17 2026-08-24 07:01 639231508078650885
570 ms 175.111.82.53
16 2026-08-24 06:44 639231498210697093
2373 ms 175.111.82.53
15 2026-08-24 06:27 639231488109699360
552 ms 175.111.82.53
14 2026-08-24 05:35 639231456772510692
550 ms 175.111.82.53
13 2026-08-24 05:18 639231447084631185
532 ms 175.111.82.53
12 2026-08-24 05:02 639231437208519473
543 ms 175.111.82.53
11 2026-08-24 04:46 639231427209627490
564 ms 175.111.82.53
10 2026-08-24 03:53 639231395791246644
590 ms 175.111.82.53
9 2026-08-24 03:37 639231386075551458
551 ms 175.111.82.53
8 2026-08-24 03:21 639231376208713791
582 ms 175.111.82.53
7 2026-08-24 03:04 639231366170589276
565 ms 175.111.82.53
6 2026-08-24 02:12 639231334732159368
564 ms 175.111.82.53
5 2026-08-24 01:55 639231325035670078
569 ms 175.111.82.53
4 2026-08-24 01:39 639231315132253837
2347 ms 175.111.82.53
3 2026-08-24 01:22 639231305014280808
556 ms 175.111.82.53
2 2026-08-24 00:30 639231273779380675
379 ms 175.111.82.53
1 2026-08-24 00:14 639231264180839154
559 ms 175.111.82.53