DNS response history for ns1.miverx.cloud

ns1.miverx.cloud 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-25. For this date, NameServerHistory found 38 DNS check records, 35 successful responses, 3 failed responses, and 1877 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 ns1.miverx.cloud.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

1877 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.60.195.8

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

3

Checks with no response or no returned latency

Failure Rate

8%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.miverx.cloud

Showing DNS history for 2026-08-25 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-25 13:01 639232587225721862
2010 ms 72.60.195.8
37 2026-08-25 12:44 639232576780683689
2032 ms 72.60.195.8
36 2026-08-25 12:26 639232566381512620
2031 ms 72.60.195.8
35 2026-08-25 12:09 639232556111768563
2007 ms 72.60.195.8
34 2026-08-25 11:52 639232545839529039
4038 ms 72.60.195.8
33 2026-08-25 11:35 639232535349285207
2007 ms 72.60.195.8
32 2026-08-25 11:17 639232524938080723
2009 ms 72.60.195.8
31 2026-08-25 10:23 639232492740373468
-
30 2026-08-25 10:06 639232482235303141
4459 ms 72.60.195.8
29 2026-08-25 09:49 639232471861770303
4039 ms 72.60.195.8
28 2026-08-25 09:32 639232461630217327
2033 ms 72.60.195.8
27 2026-08-25 09:14 639232451282965990
2220 ms 72.60.195.8
26 2026-08-25 08:57 639232440814614938
2039 ms 72.60.195.8
25 2026-08-25 08:40 639232430410720425
2007 ms 72.60.195.8
24 2026-08-25 08:22 639232420003096185
-
23 2026-08-25 08:05 639232409467287444
2264 ms 72.60.195.8
22 2026-08-25 07:48 639232399077195997
2274 ms 72.60.195.8
21 2026-08-25 07:30 639232388731528337
2007 ms 72.60.195.8
20 2026-08-25 07:13 639232378288598612
-
19 2026-08-25 06:19 639232346196373643
3 ms 72.60.195.8
18 2026-08-25 06:02 639232336112370741
2 ms 72.60.195.8
17 2026-08-25 05:45 639232326146508970
2 ms 72.60.195.8
16 2026-08-25 05:29 639232316189381720
2 ms 72.60.195.8
15 2026-08-25 05:12 639232306217998913
3 ms 72.60.195.8
14 2026-08-25 04:55 639232296255744174
2032 ms 72.60.195.8
13 2026-08-25 04:39 639232286095760789
2030 ms 72.60.195.8
12 2026-08-25 04:22 639232276086186273
2057 ms 72.60.195.8
11 2026-08-25 04:05 639232265900986425
2260 ms 72.60.195.8
10 2026-08-25 03:48 639232255723518075
2 ms 72.60.195.8
9 2026-08-25 03:31 639232245484452890
2007 ms 72.60.195.8
8 2026-08-25 03:14 639232235157175331
2 ms 72.60.195.8
7 2026-08-25 02:21 639232203197189095
2008 ms 72.60.195.8
6 2026-08-25 02:04 639232192844564298
2195 ms 72.60.195.8
5 2026-08-25 01:46 639232182496008942
2016 ms 72.60.195.8
4 2026-08-25 01:29 639232172197053132
2034 ms 72.60.195.8
3 2026-08-25 00:36 639232140250307418
2032 ms 72.60.195.8
2 2026-08-25 00:19 639232129927860324
2008 ms 72.60.195.8
1 2026-08-25 00:02 639232119551972438
3537 ms 72.60.195.8