DNS response history for ns.osan.jp

ns.osan.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 33 DNS check records, 33 successful responses, 0 failed responses, and 342 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.osan.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

342 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.130.89.61

Most recently resolved hosting IP on selected date

Successful Responses

33

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.osan.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
33 2026-08-25 11:49 639232545839529039
375 ms 133.130.89.61
32 2026-08-25 11:32 639232535349285207
191 ms 133.130.89.61
31 2026-08-25 11:14 639232524938080723
378 ms 133.130.89.61
30 2026-08-25 10:21 639232492740373468
374 ms 133.130.89.61
29 2026-08-25 10:04 639232482235303141
377 ms 133.130.89.61
28 2026-08-25 09:46 639232471861770303
411 ms 133.130.89.61
27 2026-08-25 09:29 639232461630217327
787 ms 133.130.89.61
26 2026-08-25 09:12 639232451282965990
197 ms 133.130.89.61
25 2026-08-25 08:54 639232440814614938
370 ms 133.130.89.61
24 2026-08-25 08:37 639232430410720425
382 ms 133.130.89.61
23 2026-08-25 08:20 639232420003096185
368 ms 133.130.89.61
22 2026-08-25 08:02 639232409467287444
370 ms 133.130.89.61
21 2026-08-25 07:45 639232399077195997
375 ms 133.130.89.61
20 2026-08-25 07:27 639232388731528337
355 ms 133.130.89.61
19 2026-08-25 07:10 639232378288598612
384 ms 133.130.89.61
18 2026-08-25 06:16 639232346196373643
3 ms 133.130.89.61
17 2026-08-25 05:59 639232336112370741
372 ms 133.130.89.61
16 2026-08-25 05:43 639232326146508970
375 ms 133.130.89.61
15 2026-08-25 05:26 639232316189381720
16 ms 133.130.89.61
14 2026-08-25 05:10 639232306217998913
293 ms 133.130.89.61
13 2026-08-25 04:53 639232296255744174
385 ms 133.130.89.61
12 2026-08-25 04:36 639232286095760789
191 ms 133.130.89.61
11 2026-08-25 04:19 639232276086186273
363 ms 133.130.89.61
10 2026-08-25 04:03 639232265900986425
373 ms 133.130.89.61
9 2026-08-25 03:46 639232255723518075
368 ms 133.130.89.61
8 2026-08-25 03:29 639232245484452890
365 ms 133.130.89.61
7 2026-08-25 03:11 639232235157175331
367 ms 133.130.89.61
6 2026-08-25 02:18 639232203197189095
398 ms 133.130.89.61
5 2026-08-25 02:01 639232192844564298
235 ms 133.130.89.61
4 2026-08-25 01:44 639232182496008942
373 ms 133.130.89.61
3 2026-08-25 01:26 639232172197053132
374 ms 133.130.89.61
2 2026-08-25 00:33 639232140250307418
370 ms 133.130.89.61
1 2026-08-25 00:16 639232129927860324
378 ms 133.130.89.61