DNS response history for ns2.mummyweberp.com

ns2.mummyweberp.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 34 DNS check records, 34 successful responses, 0 failed responses, and 345 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.mummyweberp.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

345 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.161.129.171

Most recently resolved hosting IP on selected date

Successful Responses

34

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.mummyweberp.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
34 2026-08-26 10:42 639233370841350248
138 ms 108.161.129.171
33 2026-08-26 10:25 639233360361507238
4 ms 108.161.129.171
32 2026-08-26 10:07 639233350067824371
127 ms 108.161.129.171
31 2026-08-26 09:50 639233339545274518
3 ms 108.161.129.171
30 2026-08-26 09:33 639233329214918079
135 ms 108.161.129.171
29 2026-08-26 09:15 639233318749762337
12 ms 108.161.129.171
28 2026-08-26 08:58 639233308387917838
271 ms 108.161.129.171
27 2026-08-26 08:41 639233297961740122
266 ms 108.161.129.171
26 2026-08-26 08:23 639233287487159094
270 ms 108.161.129.171
25 2026-08-26 08:06 639233276995531707
2008 ms 108.161.129.171
24 2026-08-26 07:48 639233266521568229
129 ms 108.161.129.171
23 2026-08-26 07:31 639233256081047431
268 ms 108.161.129.171
22 2026-08-26 06:37 639233223620132921
279 ms 108.161.129.171
21 2026-08-26 06:20 639233213287814244
277 ms 108.161.129.171
20 2026-08-26 06:02 639233202925983161
2157 ms 108.161.129.171
19 2026-08-26 05:45 639233192644780696
3 ms 108.161.129.171
18 2026-08-26 05:28 639233182401183833
132 ms 108.161.129.171
17 2026-08-26 05:11 639233172074181051
3 ms 108.161.129.171
16 2026-08-26 04:54 639233161808421455
138 ms 108.161.129.171
15 2026-08-26 04:36 639233151357344052
252 ms 108.161.129.171
14 2026-08-26 04:19 639233141034116946
264 ms 108.161.129.171
13 2026-08-26 04:02 639233130828334142
266 ms 108.161.129.171
12 2026-08-26 03:45 639233120373450007
265 ms 108.161.129.171
11 2026-08-26 03:27 639233110066216193
2186 ms 108.161.129.171
10 2026-08-26 02:34 639233078065410564
131 ms 108.161.129.171
9 2026-08-26 02:17 639233067787457832
281 ms 108.161.129.171
8 2026-08-26 02:00 639233057501801162
127 ms 108.161.129.171
7 2026-08-26 01:43 639233047089431703
126 ms 108.161.129.171
6 2026-08-26 01:25 639233036754790688
2 ms 108.161.129.171
5 2026-08-26 01:08 639233026412602472
268 ms 108.161.129.171
4 2026-08-26 00:51 639233016064066127
270 ms 108.161.129.171
3 2026-08-26 00:34 639233005922655772
274 ms 108.161.129.171
2 2026-08-26 00:17 639232995672256907
270 ms 108.161.129.171
1 2026-08-26 00:00 639232985300872416
136 ms 108.161.129.171