DNS response history for ns2.ocn.ad.jp

ns2.ocn.ad.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 346 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.ocn.ad.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

346 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.129.12.204

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.ocn.ad.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:19 639231703815441688
60 ms 211.129.12.204
29 2026-08-24 12:02 639231693747052549
55 ms 211.129.12.204
28 2026-08-24 11:46 639231683712487276
3 ms 211.129.12.204
27 2026-08-24 11:29 639231673513573868
3 ms 211.129.12.204
26 2026-08-24 10:36 639231641791249939
4 ms 211.129.12.204
25 2026-08-24 10:19 639231631866211033
6 ms 211.129.12.204
24 2026-08-24 10:02 639231621644955316
271 ms 211.129.12.204
23 2026-08-24 09:45 639231611478799259
287 ms 211.129.12.204
22 2026-08-24 08:53 639231579923718211
275 ms 211.129.12.204
21 2026-08-24 08:36 639231569810702936
259 ms 211.129.12.204
20 2026-08-24 08:19 639231559762411619
281 ms 211.129.12.204
19 2026-08-24 08:02 639231549663595407
5 ms 211.129.12.204
18 2026-08-24 07:10 639231518076817246
7 ms 211.129.12.204
17 2026-08-24 06:53 639231508078650885
262 ms 211.129.12.204
16 2026-08-24 06:36 639231498210697093
2037 ms 211.129.12.204
15 2026-08-24 06:20 639231488109699360
518 ms 211.129.12.204
14 2026-08-24 05:27 639231456772510692
263 ms 211.129.12.204
13 2026-08-24 05:11 639231447084631185
7 ms 211.129.12.204
12 2026-08-24 04:55 639231437208519473
2264 ms 211.129.12.204
11 2026-08-24 04:38 639231427209627490
7 ms 211.129.12.204
10 2026-08-24 03:46 639231395791246644
9 ms 211.129.12.204
9 2026-08-24 03:30 639231386075551458
29 ms 211.129.12.204
8 2026-08-24 03:13 639231376208713791
860 ms 211.129.12.204
7 2026-08-24 02:56 639231366170589276
7 ms 211.129.12.204
6 2026-08-24 02:04 639231334732159368
9 ms 211.129.12.204
5 2026-08-24 01:48 639231325035670078
36 ms 211.129.12.204
4 2026-08-24 01:31 639231315132253837
2009 ms 211.129.12.204
3 2026-08-24 01:15 639231305014280808
510 ms 211.129.12.204
2 2026-08-24 00:22 639231273779380675
19 ms 211.129.12.204
1 2026-08-24 00:06 639231264180839154
3 ms 211.129.12.204