DNS response history for ns2.mike3man.com

ns2.mike3man.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 227 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.mike3man.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

227 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.114.225.49

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.mike3man.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:50 639231828211839931
223 ms 45.114.225.49
37 2026-08-24 15:33 639231818080917481
279 ms 45.114.225.49
36 2026-08-24 15:16 639231807961539652
302 ms 45.114.225.49
35 2026-08-24 14:59 639231797631669865
129 ms 45.114.225.49
34 2026-08-24 14:06 639231765923559455
34 ms 45.114.225.49
33 2026-08-24 13:50 639231755868832964
14 ms 45.114.225.49
32 2026-08-24 13:33 639231745628278877
353 ms 45.114.225.49
31 2026-08-24 13:15 639231735407682062
389 ms 45.114.225.49
30 2026-08-24 12:23 639231703815441688
119 ms 45.114.225.49
29 2026-08-24 12:06 639231693747052549
287 ms 45.114.225.49
28 2026-08-24 11:49 639231683712487276
128 ms 45.114.225.49
27 2026-08-24 11:32 639231673513573868
2 ms 45.114.225.49
26 2026-08-24 10:39 639231641791249939
6 ms 45.114.225.49
25 2026-08-24 10:23 639231631866211033
295 ms 45.114.225.49
24 2026-08-24 10:06 639231621644955316
381 ms 45.114.225.49
23 2026-08-24 09:49 639231611478799259
310 ms 45.114.225.49
22 2026-08-24 08:56 639231579923718211
141 ms 45.114.225.49
21 2026-08-24 08:40 639231569810702936
286 ms 45.114.225.49
20 2026-08-24 08:23 639231559762411619
282 ms 45.114.225.49
19 2026-08-24 08:06 639231549663595407
149 ms 45.114.225.49
18 2026-08-24 07:13 639231518076817246
320 ms 45.114.225.49
17 2026-08-24 06:57 639231508078650885
193 ms 45.114.225.49
16 2026-08-24 06:40 639231498210697093
2253 ms 45.114.225.49
15 2026-08-24 06:24 639231488109699360
311 ms 45.114.225.49
14 2026-08-24 05:31 639231456772510692
285 ms 45.114.225.49
13 2026-08-24 05:15 639231447084631185
4 ms 45.114.225.49
12 2026-08-24 04:58 639231437208519473
7 ms 45.114.225.49
11 2026-08-24 04:42 639231427209627490
4 ms 45.114.225.49
10 2026-08-24 03:49 639231395791246644
126 ms 45.114.225.49
9 2026-08-24 03:33 639231386075551458
5 ms 45.114.225.49
8 2026-08-24 03:17 639231376208713791
3 ms 45.114.225.49
7 2026-08-24 03:00 639231366170589276
312 ms 45.114.225.49
6 2026-08-24 02:08 639231334732159368
2 ms 45.114.225.49
5 2026-08-24 01:51 639231325035670078
317 ms 45.114.225.49
4 2026-08-24 01:35 639231315132253837
105 ms 45.114.225.49
3 2026-08-24 01:18 639231305014280808
275 ms 45.114.225.49
2 2026-08-24 00:26 639231273779380675
4 ms 45.114.225.49
1 2026-08-24 00:10 639231264180839154
2 ms 45.114.225.49