DNS response history for ns3.mmaxrp.com

ns3.mmaxrp.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 391 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 ns3.mmaxrp.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

391 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.152.38.5

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 ns3.mmaxrp.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 11:36 639233403515141099
225 ms 107.152.38.5
33 2026-08-26 10:41 639233370841350248
107 ms 107.152.38.5
32 2026-08-26 10:24 639233360361507238
597 ms 107.152.38.5
31 2026-08-26 10:06 639233350067824371
211 ms 107.152.38.5
30 2026-08-26 09:49 639233339545274518
206 ms 107.152.38.5
29 2026-08-26 09:32 639233329214918079
104 ms 107.152.38.5
28 2026-08-26 09:14 639233318749762337
208 ms 107.152.38.5
27 2026-08-26 08:57 639233308387917838
206 ms 107.152.38.5
26 2026-08-26 08:40 639233297961740122
217 ms 107.152.38.5
25 2026-08-26 08:22 639233287487159094
101 ms 107.152.38.5
24 2026-08-26 08:05 639233276995531707
204 ms 107.152.38.5
23 2026-08-26 07:47 639233266521568229
2119 ms 107.152.38.5
22 2026-08-26 07:30 639233256081047431
160 ms 107.152.38.5
21 2026-08-26 06:36 639233223620132921
213 ms 107.152.38.5
20 2026-08-26 06:18 639233213287814244
206 ms 107.152.38.5
19 2026-08-26 06:01 639233202925983161
106 ms 107.152.38.5
18 2026-08-26 05:44 639233192644780696
104 ms 107.152.38.5
17 2026-08-26 05:27 639233182401183833
208 ms 107.152.38.5
16 2026-08-26 05:10 639233172074181051
103 ms 107.152.38.5
15 2026-08-26 04:53 639233161808421455
104 ms 107.152.38.5
14 2026-08-26 04:35 639233151357344052
104 ms 107.152.38.5
13 2026-08-26 04:18 639233141034116946
204 ms 107.152.38.5
12 2026-08-26 04:01 639233130828334142
209 ms 107.152.38.5
11 2026-08-26 03:44 639233120373450007
1617 ms 107.152.38.5
10 2026-08-26 03:26 639233110066216193
204 ms 107.152.38.5
9 2026-08-26 02:33 639233078065410564
211 ms 107.152.38.5
8 2026-08-26 02:16 639233067787457832
104 ms 107.152.38.5
7 2026-08-26 01:59 639233057501801162
3700 ms 107.152.38.5
6 2026-08-26 01:42 639233047089431703
210 ms 107.152.38.5
5 2026-08-26 01:24 639233036754790688
205 ms 107.152.38.5
4 2026-08-26 01:07 639233026412602472
209 ms 107.152.38.5
3 2026-08-26 00:50 639233016064066127
202 ms 107.152.38.5
2 2026-08-26 00:33 639233005922655772
206 ms 107.152.38.5
1 2026-08-26 00:16 639232995672256907
208 ms 107.152.38.5