DNS response history for ns1.openreaf.jp

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

28

Historical checks stored for this nameserver on selected date

Average Latency

569 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.138.124.196

Most recently resolved hosting IP on selected date

Successful Responses

28

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.openreaf.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
28 2026-08-25 09:30 639232461630217327
555 ms 203.138.124.196
27 2026-08-25 09:13 639232451282965990
569 ms 203.138.124.196
26 2026-08-25 08:55 639232440814614938
536 ms 203.138.124.196
25 2026-08-25 08:38 639232430410720425
564 ms 203.138.124.196
24 2026-08-25 08:21 639232420003096185
543 ms 203.138.124.196
23 2026-08-25 08:03 639232409467287444
538 ms 203.138.124.196
22 2026-08-25 07:46 639232399077195997
542 ms 203.138.124.196
21 2026-08-25 07:28 639232388731528337
812 ms 203.138.124.196
20 2026-08-25 07:11 639232378288598612
535 ms 203.138.124.196
19 2026-08-25 06:17 639232346196373643
552 ms 203.138.124.196
18 2026-08-25 06:01 639232336112370741
5 ms 203.138.124.196
17 2026-08-25 05:44 639232326146508970
1360 ms 203.138.124.196
16 2026-08-25 05:27 639232316189381720
1360 ms 203.138.124.196
15 2026-08-25 05:11 639232306217998913
639 ms 203.138.124.196
14 2026-08-25 04:54 639232296255744174
538 ms 203.138.124.196
13 2026-08-25 04:37 639232286095760789
3 ms 203.138.124.196
12 2026-08-25 04:20 639232276086186273
552 ms 203.138.124.196
11 2026-08-25 04:04 639232265900986425
551 ms 203.138.124.196
10 2026-08-25 03:47 639232255723518075
551 ms 203.138.124.196
9 2026-08-25 03:30 639232245484452890
549 ms 203.138.124.196
8 2026-08-25 03:13 639232235157175331
553 ms 203.138.124.196
7 2026-08-25 02:19 639232203197189095
3 ms 203.138.124.196
6 2026-08-25 02:02 639232192844564298
3 ms 203.138.124.196
5 2026-08-25 01:45 639232182496008942
560 ms 203.138.124.196
4 2026-08-25 01:28 639232172197053132
536 ms 203.138.124.196
3 2026-08-25 00:34 639232140250307418
532 ms 203.138.124.196
2 2026-08-25 00:17 639232129927860324
540 ms 203.138.124.196
1 2026-08-25 00:00 639232119551972438
1340 ms 203.138.124.196