DNS response history for ns4.maid-san.jp

ns4.maid-san.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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 581 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 ns4.maid-san.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

581 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.94.235.37

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 ns4.maid-san.jp

Showing DNS history for 2026-08-26 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-26 09:01 639233308387917838
562 ms 219.94.235.37
27 2026-08-26 08:44 639233297961740122
553 ms 219.94.235.37
26 2026-08-26 08:26 639233287487159094
548 ms 219.94.235.37
25 2026-08-26 08:09 639233276995531707
542 ms 219.94.235.37
24 2026-08-26 07:51 639233266521568229
553 ms 219.94.235.37
23 2026-08-26 07:34 639233256081047431
554 ms 219.94.235.37
22 2026-08-26 06:40 639233223620132921
458 ms 219.94.235.37
21 2026-08-26 06:23 639233213287814244
554 ms 219.94.235.37
20 2026-08-26 06:05 639233202925983161
542 ms 219.94.235.37
19 2026-08-26 05:48 639233192644780696
467 ms 219.94.235.37
18 2026-08-26 05:31 639233182401183833
555 ms 219.94.235.37
17 2026-08-26 05:14 639233172074181051
2276 ms 219.94.235.37
16 2026-08-26 04:57 639233161808421455
448 ms 219.94.235.37
15 2026-08-26 04:39 639233151357344052
550 ms 219.94.235.37
14 2026-08-26 04:22 639233141034116946
484 ms 219.94.235.37
13 2026-08-26 04:05 639233130828334142
545 ms 219.94.235.37
12 2026-08-26 03:48 639233120373450007
543 ms 219.94.235.37
11 2026-08-26 03:30 639233110066216193
542 ms 219.94.235.37
10 2026-08-26 02:37 639233078065410564
530 ms 219.94.235.37
9 2026-08-26 02:20 639233067787457832
4 ms 219.94.235.37
8 2026-08-26 02:03 639233057501801162
515 ms 219.94.235.37
7 2026-08-26 01:46 639233047089431703
548 ms 219.94.235.37
6 2026-08-26 01:28 639233036754790688
559 ms 219.94.235.37
5 2026-08-26 01:11 639233026412602472
480 ms 219.94.235.37
4 2026-08-26 00:54 639233016064066127
551 ms 219.94.235.37
3 2026-08-26 00:37 639233005922655772
765 ms 219.94.235.37
2 2026-08-26 00:20 639232995672256907
541 ms 219.94.235.37
1 2026-08-26 00:03 639232985300872416
504 ms 219.94.235.37