DNS response history for ns3.maxumdata.net

ns3.maxumdata.net 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 412 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.maxumdata.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

412 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

43.252.71.50

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.maxumdata.net

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:44 639233370841350248
287 ms 43.252.71.50
33 2026-08-26 10:27 639233360361507238
559 ms 43.252.71.50
32 2026-08-26 10:09 639233350067824371
296 ms 43.252.71.50
31 2026-08-26 09:52 639233339545274518
564 ms 43.252.71.50
30 2026-08-26 09:35 639233329214918079
577 ms 43.252.71.50
29 2026-08-26 09:17 639233318749762337
569 ms 43.252.71.50
28 2026-08-26 09:00 639233308387917838
287 ms 43.252.71.50
27 2026-08-26 08:43 639233297961740122
296 ms 43.252.71.50
26 2026-08-26 08:25 639233287487159094
568 ms 43.252.71.50
25 2026-08-26 08:08 639233276995531707
280 ms 43.252.71.50
24 2026-08-26 07:50 639233266521568229
283 ms 43.252.71.50
23 2026-08-26 07:33 639233256081047431
561 ms 43.252.71.50
22 2026-08-26 06:39 639233223620132921
292 ms 43.252.71.50
21 2026-08-26 06:22 639233213287814244
281 ms 43.252.71.50
20 2026-08-26 06:04 639233202925983161
557 ms 43.252.71.50
19 2026-08-26 05:47 639233192644780696
3 ms 43.252.71.50
18 2026-08-26 05:30 639233182401183833
281 ms 43.252.71.50
17 2026-08-26 05:13 639233172074181051
566 ms 43.252.71.50
16 2026-08-26 04:56 639233161808421455
572 ms 43.252.71.50
15 2026-08-26 04:39 639233151357344052
567 ms 43.252.71.50
14 2026-08-26 04:21 639233141034116946
564 ms 43.252.71.50
13 2026-08-26 04:04 639233130828334142
565 ms 43.252.71.50
12 2026-08-26 03:47 639233120373450007
568 ms 43.252.71.50
11 2026-08-26 03:29 639233110066216193
334 ms 43.252.71.50
10 2026-08-26 02:36 639233078065410564
295 ms 43.252.71.50
9 2026-08-26 02:19 639233067787457832
280 ms 43.252.71.50
8 2026-08-26 02:02 639233057501801162
558 ms 43.252.71.50
7 2026-08-26 01:45 639233047089431703
297 ms 43.252.71.50
6 2026-08-26 01:27 639233036754790688
281 ms 43.252.71.50
5 2026-08-26 01:10 639233026412602472
574 ms 43.252.71.50
4 2026-08-26 00:53 639233016064066127
285 ms 43.252.71.50
3 2026-08-26 00:36 639233005922655772
577 ms 43.252.71.50
2 2026-08-26 00:19 639232995672256907
286 ms 43.252.71.50
1 2026-08-26 00:02 639232985300872416
281 ms 43.252.71.50