DNS response history for ns2.miverx.site

ns2.miverx.site 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 39 DNS check records, 27 successful responses, 12 failed responses, and 346 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.miverx.site.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

346 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.164.250.220

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

12

Checks with no response or no returned latency

Failure Rate

31%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.miverx.site

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
39 2026-08-24 16:47 639231860258429562
-
38 2026-08-24 15:53 639231828211839931
-
37 2026-08-24 15:37 639231818080917481
-
36 2026-08-24 15:20 639231807961539652
-
35 2026-08-24 15:03 639231797631669865
-
34 2026-08-24 14:10 639231765923559455
-
33 2026-08-24 13:53 639231755868832964
-
32 2026-08-24 13:36 639231745628278877
-
31 2026-08-24 13:19 639231735407682062
-
30 2026-08-24 12:26 639231703815441688
-
29 2026-08-24 12:09 639231693747052549
6 ms 69.164.250.220
28 2026-08-24 11:52 639231683712487276
-
27 2026-08-24 11:36 639231673513573868
-
26 2026-08-24 10:42 639231641791249939
258 ms 69.164.250.220
25 2026-08-24 10:26 639231631866211033
252 ms 69.164.250.220
24 2026-08-24 10:09 639231621644955316
256 ms 69.164.250.220
23 2026-08-24 09:52 639231611478799259
4 ms 69.164.250.220
22 2026-08-24 08:59 639231579923718211
3 ms 69.164.250.220
21 2026-08-24 08:43 639231569810702936
253 ms 69.164.250.220
20 2026-08-24 08:26 639231559762411619
3 ms 69.164.250.220
19 2026-08-24 08:09 639231549663595407
3 ms 69.164.250.220
18 2026-08-24 07:16 639231518076817246
254 ms 69.164.250.220
17 2026-08-24 07:00 639231508078650885
3 ms 69.164.250.220
16 2026-08-24 06:43 639231498210697093
253 ms 69.164.250.220
15 2026-08-24 06:26 639231488109699360
4 ms 69.164.250.220
14 2026-08-24 05:34 639231456772510692
251 ms 69.164.250.220
13 2026-08-24 05:18 639231447084631185
257 ms 69.164.250.220
12 2026-08-24 05:01 639231437208519473
2248 ms 69.164.250.220
11 2026-08-24 04:45 639231427209627490
259 ms 69.164.250.220
10 2026-08-24 03:52 639231395791246644
3 ms 69.164.250.220
9 2026-08-24 03:36 639231386075551458
3 ms 69.164.250.220
8 2026-08-24 03:20 639231376208713791
2 ms 69.164.250.220
7 2026-08-24 03:03 639231366170589276
4246 ms 69.164.250.220
6 2026-08-24 02:11 639231334732159368
258 ms 69.164.250.220
5 2026-08-24 01:54 639231325035670078
3 ms 69.164.250.220
4 2026-08-24 01:38 639231315132253837
3 ms 69.164.250.220
3 2026-08-24 01:21 639231305014280808
252 ms 69.164.250.220
2 2026-08-24 00:29 639231273779380675
3 ms 69.164.250.220
1 2026-08-24 00:13 639231264180839154
2 ms 69.164.250.220