DNS response history for ns2.mike-white.net

ns2.mike-white.net 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 37 DNS check records, 37 successful responses, 0 failed responses, and 403 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.mike-white.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

403 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.79.78

Most recently resolved hosting IP on selected date

Successful Responses

37

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.mike-white.net

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
37 2026-08-24 15:35 639231818080917481
430 ms 162.240.79.78
36 2026-08-24 15:18 639231807961539652
159 ms 162.240.79.78
35 2026-08-24 15:01 639231797631669865
434 ms 162.240.79.78
34 2026-08-24 14:08 639231765923559455
3 ms 162.240.79.78
33 2026-08-24 13:51 639231755868832964
447 ms 162.240.79.78
32 2026-08-24 13:35 639231745628278877
440 ms 162.240.79.78
31 2026-08-24 13:17 639231735407682062
435 ms 162.240.79.78
30 2026-08-24 12:25 639231703815441688
436 ms 162.240.79.78
29 2026-08-24 12:08 639231693747052549
433 ms 162.240.79.78
28 2026-08-24 11:51 639231683712487276
151 ms 162.240.79.78
27 2026-08-24 11:34 639231673513573868
2009 ms 162.240.79.78
26 2026-08-24 10:41 639231641791249939
437 ms 162.240.79.78
25 2026-08-24 10:25 639231631866211033
635 ms 162.240.79.78
24 2026-08-24 10:08 639231621644955316
432 ms 162.240.79.78
23 2026-08-24 09:51 639231611478799259
154 ms 162.240.79.78
22 2026-08-24 08:58 639231579923718211
5 ms 162.240.79.78
21 2026-08-24 08:42 639231569810702936
436 ms 162.240.79.78
20 2026-08-24 08:24 639231559762411619
2009 ms 162.240.79.78
19 2026-08-24 08:08 639231549663595407
2004 ms 162.240.79.78
18 2026-08-24 07:15 639231518076817246
3 ms 162.240.79.78
17 2026-08-24 06:59 639231508078650885
4 ms 162.240.79.78
16 2026-08-24 06:42 639231498210697093
433 ms 162.240.79.78
15 2026-08-24 06:25 639231488109699360
437 ms 162.240.79.78
14 2026-08-24 05:33 639231456772510692
3 ms 162.240.79.78
13 2026-08-24 05:17 639231447084631185
4 ms 162.240.79.78
12 2026-08-24 05:00 639231437208519473
439 ms 162.240.79.78
11 2026-08-24 04:44 639231427209627490
162 ms 162.240.79.78
10 2026-08-24 03:51 639231395791246644
433 ms 162.240.79.78
9 2026-08-24 03:35 639231386075551458
437 ms 162.240.79.78
8 2026-08-24 03:19 639231376208713791
3 ms 162.240.79.78
7 2026-08-24 03:02 639231366170589276
2 ms 162.240.79.78
6 2026-08-24 02:10 639231334732159368
4 ms 162.240.79.78
5 2026-08-24 01:53 639231325035670078
3 ms 162.240.79.78
4 2026-08-24 01:37 639231315132253837
202 ms 162.240.79.78
3 2026-08-24 01:20 639231305014280808
2 ms 162.240.79.78
2 2026-08-24 00:28 639231273779380675
431 ms 162.240.79.78
1 2026-08-24 00:12 639231264180839154
434 ms 162.240.79.78