DNS response history for ns1.netowl.jp

ns1.netowl.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 30 DNS check records, 30 successful responses, 0 failed responses, and 416 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 ns1.netowl.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

416 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.43.112.86

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 ns1.netowl.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
30 2026-08-25 10:21 639232492740373468
741 ms 162.43.112.86
29 2026-08-25 10:04 639232482235303141
495 ms 162.43.112.86
28 2026-08-25 09:46 639232471861770303
254 ms 162.43.112.86
27 2026-08-25 09:29 639232461630217327
238 ms 162.43.112.86
26 2026-08-25 09:12 639232451282965990
506 ms 162.43.112.86
25 2026-08-25 08:55 639232440814614938
277 ms 162.43.112.86
24 2026-08-25 08:37 639232430410720425
494 ms 162.43.112.86
23 2026-08-25 08:20 639232420003096185
501 ms 162.43.112.86
22 2026-08-25 08:02 639232409467287444
257 ms 162.43.112.86
21 2026-08-25 07:45 639232399077195997
258 ms 162.43.112.86
20 2026-08-25 07:27 639232388731528337
497 ms 162.43.112.86
19 2026-08-25 07:10 639232378288598612
506 ms 162.43.112.86
18 2026-08-25 06:16 639232346196373643
249 ms 162.43.112.86
17 2026-08-25 06:00 639232336112370741
491 ms 162.43.112.86
16 2026-08-25 05:43 639232326146508970
481 ms 162.43.112.86
15 2026-08-25 05:26 639232316189381720
498 ms 162.43.112.86
14 2026-08-25 05:10 639232306217998913
492 ms 162.43.112.86
13 2026-08-25 04:53 639232296255744174
248 ms 162.43.112.86
12 2026-08-25 04:36 639232286095760789
493 ms 162.43.112.86
11 2026-08-25 04:19 639232276086186273
501 ms 162.43.112.86
10 2026-08-25 04:03 639232265900986425
504 ms 162.43.112.86
9 2026-08-25 03:46 639232255723518075
502 ms 162.43.112.86
8 2026-08-25 03:29 639232245484452890
238 ms 162.43.112.86
7 2026-08-25 03:12 639232235157175331
489 ms 162.43.112.86
6 2026-08-25 02:18 639232203197189095
247 ms 162.43.112.86
5 2026-08-25 02:01 639232192844564298
510 ms 162.43.112.86
4 2026-08-25 01:44 639232182496008942
246 ms 162.43.112.86
3 2026-08-25 01:27 639232172197053132
509 ms 162.43.112.86
2 2026-08-25 00:33 639232140250307418
504 ms 162.43.112.86
1 2026-08-25 00:16 639232129927860324
247 ms 162.43.112.86