DNS response history for ns2.mikaze.jp

ns2.mikaze.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 446 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 ns2.mikaze.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

446 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.247.81.99

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns2.mikaze.jp

Showing DNS history for 2026-08-24 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
36 2026-08-24 15:13 639231807961539652
24 ms 104.247.81.99
35 2026-08-24 14:56 639231797631669865
20 ms 104.247.81.99
34 2026-08-24 14:03 639231765923559455
23 ms 104.247.81.99
33 2026-08-24 13:46 639231755868832964
104 ms 104.247.81.99
32 2026-08-24 13:29 639231745628278877
44 ms 104.247.81.99
31 2026-08-24 13:12 639231735407682062
2016 ms 104.247.81.99
30 2026-08-24 12:19 639231703815441688
2023 ms 104.247.81.99
29 2026-08-24 12:03 639231693747052549
31 ms 104.247.81.99
28 2026-08-24 11:46 639231683712487276
16 ms 104.247.81.99
27 2026-08-24 11:29 639231673513573868
374 ms 104.247.81.99
26 2026-08-24 10:36 639231641791249939
24 ms 104.247.81.99
25 2026-08-24 10:19 639231631866211033
44 ms 104.247.81.99
24 2026-08-24 10:03 639231621644955316
273 ms 104.247.81.99
23 2026-08-24 09:46 639231611478799259
31 ms 104.247.81.99
22 2026-08-24 08:53 639231579923718211
310 ms 104.247.81.99
21 2026-08-24 08:36 639231569810702936
2655 ms 104.247.81.99
20 2026-08-24 08:19 639231559762411619
55 ms 104.247.81.99
19 2026-08-24 08:03 639231549663595407
45 ms 104.247.81.99
18 2026-08-24 07:10 639231518076817246
271 ms 104.247.81.99
17 2026-08-24 06:54 639231508078650885
132 ms 104.247.81.99
16 2026-08-24 06:37 639231498210697093
33 ms 104.247.81.99
15 2026-08-24 06:20 639231488109699360
20 ms 104.247.81.99
14 2026-08-24 05:28 639231456772510692
4 ms 104.247.81.99
13 2026-08-24 05:12 639231447084631185
4007 ms 104.247.81.99
12 2026-08-24 04:55 639231437208519473
44 ms 104.247.81.99
11 2026-08-24 04:38 639231427209627490
34 ms 104.247.81.99
10 2026-08-24 03:46 639231395791246644
7 ms 104.247.81.99
9 2026-08-24 03:30 639231386075551458
41 ms 104.247.81.99
8 2026-08-24 03:14 639231376208713791
43 ms 104.247.81.99
7 2026-08-24 02:57 639231366170589276
64 ms 104.247.81.99
6 2026-08-24 02:05 639231334732159368
18 ms 104.247.81.99
5 2026-08-24 01:48 639231325035670078
111 ms 104.247.81.99
4 2026-08-24 01:32 639231315132253837
3045 ms 104.247.81.99
3 2026-08-24 01:15 639231305014280808
43 ms 104.247.81.99
2 2026-08-24 00:23 639231273779380675
8 ms 104.247.81.99
1 2026-08-24 00:07 639231264180839154
5 ms 104.247.81.99