DNS response history for ns2.mikebashi.com

ns2.mikebashi.com 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 38 DNS check records, 38 successful responses, 0 failed responses, and 457 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.mikebashi.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

457 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.175.8.18

Most recently resolved hosting IP on selected date

Successful Responses

38

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.mikebashi.com

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
38 2026-08-24 15:49 639231828211839931
2008 ms 107.175.8.18
37 2026-08-24 15:32 639231818080917481
281 ms 107.175.8.18
36 2026-08-24 15:15 639231807961539652
11 ms 107.175.8.18
35 2026-08-24 14:58 639231797631669865
306 ms 107.175.8.18
34 2026-08-24 14:05 639231765923559455
287 ms 107.175.8.18
33 2026-08-24 13:49 639231755868832964
2167 ms 107.175.8.18
32 2026-08-24 13:31 639231745628278877
286 ms 107.175.8.18
31 2026-08-24 13:14 639231735407682062
171 ms 107.175.8.18
30 2026-08-24 12:22 639231703815441688
151 ms 107.175.8.18
29 2026-08-24 12:05 639231693747052549
138 ms 107.175.8.18
28 2026-08-24 11:48 639231683712487276
283 ms 107.175.8.18
27 2026-08-24 11:31 639231673513573868
178 ms 107.175.8.18
26 2026-08-24 10:38 639231641791249939
289 ms 107.175.8.18
25 2026-08-24 10:22 639231631866211033
277 ms 107.175.8.18
24 2026-08-24 10:05 639231621644955316
300 ms 107.175.8.18
23 2026-08-24 09:48 639231611478799259
288 ms 107.175.8.18
22 2026-08-24 08:55 639231579923718211
2277 ms 107.175.8.18
21 2026-08-24 08:38 639231569810702936
189 ms 107.175.8.18
20 2026-08-24 08:21 639231559762411619
281 ms 107.175.8.18
19 2026-08-24 08:05 639231549663595407
283 ms 107.175.8.18
18 2026-08-24 07:12 639231518076817246
13 ms 107.175.8.18
17 2026-08-24 06:56 639231508078650885
288 ms 107.175.8.18
16 2026-08-24 06:39 639231498210697093
281 ms 107.175.8.18
15 2026-08-24 06:22 639231488109699360
177 ms 107.175.8.18
14 2026-08-24 05:30 639231456772510692
4 ms 107.175.8.18
13 2026-08-24 05:14 639231447084631185
293 ms 107.175.8.18
12 2026-08-24 04:57 639231437208519473
285 ms 107.175.8.18
11 2026-08-24 04:41 639231427209627490
281 ms 107.175.8.18
10 2026-08-24 03:48 639231395791246644
2269 ms 107.175.8.18
9 2026-08-24 03:32 639231386075551458
12 ms 107.175.8.18
8 2026-08-24 03:16 639231376208713791
9 ms 107.175.8.18
7 2026-08-24 02:59 639231366170589276
2 ms 107.175.8.18
6 2026-08-24 02:07 639231334732159368
167 ms 107.175.8.18
5 2026-08-24 01:50 639231325035670078
2137 ms 107.175.8.18
4 2026-08-24 01:34 639231315132253837
253 ms 107.175.8.18
3 2026-08-24 01:17 639231305014280808
177 ms 107.175.8.18
2 2026-08-24 00:25 639231273779380675
280 ms 107.175.8.18
1 2026-08-24 00:09 639231264180839154
3 ms 107.175.8.18