DNS response history for ns31.100mwh.com

ns31.100mwh.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 420 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 ns31.100mwh.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

420 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.64.52.106

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns31.100mwh.com

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:31 639233370841350248
37 ms 172.64.52.106
32 2026-08-26 10:14 639233360361507238
59 ms 172.64.52.106
31 2026-08-26 09:57 639233350067824371
23 ms 172.64.52.106
30 2026-08-26 09:39 639233339545274518
2043 ms 172.64.52.106
29 2026-08-26 09:22 639233329214918079
150 ms 172.64.52.106
28 2026-08-26 09:04 639233318749762337
5 ms 172.64.52.106
27 2026-08-26 08:47 639233308387917838
71 ms 172.64.52.106
26 2026-08-26 08:30 639233297961740122
80 ms 172.64.52.106
25 2026-08-26 08:12 639233287487159094
35 ms 172.64.52.106
24 2026-08-26 07:55 639233276995531707
4085 ms 172.64.52.106
23 2026-08-26 07:37 639233266521568229
41 ms 172.64.52.106
22 2026-08-26 07:20 639233256081047431
83 ms 172.64.52.106
21 2026-08-26 06:26 639233223620132921
78 ms 172.64.52.106
20 2026-08-26 06:09 639233213287814244
67 ms 172.64.52.106
19 2026-08-26 05:51 639233202925983161
41 ms 172.64.52.106
18 2026-08-26 05:34 639233192644780696
2071 ms 172.64.52.106
17 2026-08-26 05:17 639233182401183833
71 ms 172.64.52.106
16 2026-08-26 05:00 639233172074181051
47 ms 172.64.52.106
15 2026-08-26 04:43 639233161808421455
91 ms 172.64.52.106
14 2026-08-26 04:25 639233151357344052
64 ms 172.64.52.106
13 2026-08-26 04:08 639233141034116946
83 ms 172.64.52.106
12 2026-08-26 03:51 639233130828334142
69 ms 172.64.52.106
11 2026-08-26 03:34 639233120373450007
4 ms 172.64.52.106
10 2026-08-26 03:17 639233110066216193
99 ms 172.64.52.106
9 2026-08-26 02:23 639233078065410564
56 ms 172.64.52.106
8 2026-08-26 02:06 639233067787457832
2019 ms 172.64.52.106
7 2026-08-26 01:49 639233057501801162
56 ms 172.64.52.106
6 2026-08-26 01:32 639233047089431703
35 ms 172.64.52.106
5 2026-08-26 01:15 639233036754790688
2082 ms 172.64.52.106
4 2026-08-26 00:57 639233026412602472
5 ms 172.64.52.106
3 2026-08-26 00:40 639233016064066127
67 ms 172.64.52.106
2 2026-08-26 00:23 639233005922655772
6 ms 172.64.52.106
1 2026-08-26 00:06 639232995672256907
30 ms 172.64.52.106