DNS response history for ns-tkb02.ocn.ad.jp

ns-tkb02.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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 314 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 ns-tkb02.ocn.ad.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

314 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.112.46.38

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns-tkb02.ocn.ad.jp

Showing DNS history for 2026-08-25 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
37 2026-08-25 12:57 639232587225721862
402 ms 61.112.46.38
36 2026-08-25 12:40 639232576780683689
9 ms 61.112.46.38
35 2026-08-25 12:22 639232566381512620
280 ms 61.112.46.38
34 2026-08-25 12:05 639232556111768563
254 ms 61.112.46.38
33 2026-08-25 11:48 639232545839529039
253 ms 61.112.46.38
32 2026-08-25 11:31 639232535349285207
15 ms 61.112.46.38
31 2026-08-25 11:13 639232524938080723
9 ms 61.112.46.38
30 2026-08-25 10:19 639232492740373468
3 ms 61.112.46.38
29 2026-08-25 10:02 639232482235303141
263 ms 61.112.46.38
28 2026-08-25 09:45 639232471861770303
258 ms 61.112.46.38
27 2026-08-25 09:28 639232461630217327
4 ms 61.112.46.38
26 2026-08-25 09:10 639232451282965990
10 ms 61.112.46.38
25 2026-08-25 08:53 639232440814614938
265 ms 61.112.46.38
24 2026-08-25 08:36 639232430410720425
257 ms 61.112.46.38
23 2026-08-25 08:18 639232420003096185
2241 ms 61.112.46.38
22 2026-08-25 08:01 639232409467287444
259 ms 61.112.46.38
21 2026-08-25 07:43 639232399077195997
260 ms 61.112.46.38
20 2026-08-25 07:26 639232388731528337
2270 ms 61.112.46.38
19 2026-08-25 07:09 639232378288598612
256 ms 61.112.46.38
18 2026-08-25 06:15 639232346196373643
353 ms 61.112.46.38
17 2026-08-25 05:58 639232336112370741
256 ms 61.112.46.38
16 2026-08-25 05:42 639232326146508970
297 ms 61.112.46.38
15 2026-08-25 05:25 639232316189381720
4 ms 61.112.46.38
14 2026-08-25 05:08 639232306217998913
263 ms 61.112.46.38
13 2026-08-25 04:52 639232296255744174
266 ms 61.112.46.38
12 2026-08-25 04:35 639232286095760789
3 ms 61.112.46.38
11 2026-08-25 04:18 639232276086186273
254 ms 61.112.46.38
10 2026-08-25 04:01 639232265900986425
263 ms 61.112.46.38
9 2026-08-25 03:44 639232255723518075
252 ms 61.112.46.38
8 2026-08-25 03:27 639232245484452890
260 ms 61.112.46.38
7 2026-08-25 03:10 639232235157175331
271 ms 61.112.46.38
6 2026-08-25 02:17 639232203197189095
258 ms 61.112.46.38
5 2026-08-25 02:00 639232192844564298
271 ms 61.112.46.38
4 2026-08-25 01:42 639232182496008942
2 ms 61.112.46.38
3 2026-08-25 01:25 639232172197053132
261 ms 61.112.46.38
2 2026-08-25 00:32 639232140250307418
258 ms 61.112.46.38
1 2026-08-25 00:15 639232129927860324
257 ms 61.112.46.38