DNS response history for hato2.sainet.or.jp

hato2.sainet.or.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 29 DNS check records, 29 successful responses, 0 failed responses, and 560 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 hato2.sainet.or.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

560 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.236.40.138

Most recently resolved hosting IP on selected date

Successful Responses

29

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 hato2.sainet.or.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
29 2026-08-25 09:47 639232471861770303
793 ms 210.236.40.138
28 2026-08-25 09:30 639232461630217327
540 ms 210.236.40.138
27 2026-08-25 09:12 639232451282965990
541 ms 210.236.40.138
26 2026-08-25 08:55 639232440814614938
535 ms 210.236.40.138
25 2026-08-25 08:38 639232430410720425
535 ms 210.236.40.138
24 2026-08-25 08:20 639232420003096185
539 ms 210.236.40.138
23 2026-08-25 08:03 639232409467287444
543 ms 210.236.40.138
22 2026-08-25 07:46 639232399077195997
542 ms 210.236.40.138
21 2026-08-25 07:28 639232388731528337
278 ms 210.236.40.138
20 2026-08-25 07:11 639232378288598612
577 ms 210.236.40.138
19 2026-08-25 06:17 639232346196373643
584 ms 210.236.40.138
18 2026-08-25 06:00 639232336112370741
534 ms 210.236.40.138
17 2026-08-25 05:44 639232326146508970
543 ms 210.236.40.138
16 2026-08-25 05:27 639232316189381720
554 ms 210.236.40.138
15 2026-08-25 05:10 639232306217998913
781 ms 210.236.40.138
14 2026-08-25 04:54 639232296255744174
539 ms 210.236.40.138
13 2026-08-25 04:37 639232286095760789
536 ms 210.236.40.138
12 2026-08-25 04:20 639232276086186273
530 ms 210.236.40.138
11 2026-08-25 04:03 639232265900986425
274 ms 210.236.40.138
10 2026-08-25 03:46 639232255723518075
552 ms 210.236.40.138
9 2026-08-25 03:29 639232245484452890
281 ms 210.236.40.138
8 2026-08-25 03:12 639232235157175331
1300 ms 210.236.40.138
7 2026-08-25 02:19 639232203197189095
813 ms 210.236.40.138
6 2026-08-25 02:02 639232192844564298
536 ms 210.236.40.138
5 2026-08-25 01:45 639232182496008942
267 ms 210.236.40.138
4 2026-08-25 01:27 639232172197053132
554 ms 210.236.40.138
3 2026-08-25 00:34 639232140250307418
548 ms 210.236.40.138
2 2026-08-25 00:17 639232129927860324
551 ms 210.236.40.138
1 2026-08-25 00:00 639232119551972438
547 ms 210.236.40.138