DNS response history for ns3.maximlogic.com

ns3.maximlogic.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 344 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.maximlogic.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

344 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

173.0.137.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.maximlogic.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
238 ms 173.0.137.5
33 2026-08-26 10:25 639233360361507238
364 ms 173.0.137.5
32 2026-08-26 10:07 639233350067824371
30 ms 173.0.137.5
31 2026-08-26 09:50 639233339545274518
176 ms 173.0.137.5
30 2026-08-26 09:33 639233329214918079
192 ms 173.0.137.5
29 2026-08-26 09:15 639233318749762337
254 ms 173.0.137.5
28 2026-08-26 08:58 639233308387917838
241 ms 173.0.137.5
27 2026-08-26 08:41 639233297961740122
241 ms 173.0.137.5
26 2026-08-26 08:23 639233287487159094
242 ms 173.0.137.5
25 2026-08-26 08:06 639233276995531707
368 ms 173.0.137.5
24 2026-08-26 07:48 639233266521568229
243 ms 173.0.137.5
23 2026-08-26 07:31 639233256081047431
242 ms 173.0.137.5
22 2026-08-26 06:37 639233223620132921
643 ms 173.0.137.5
21 2026-08-26 06:20 639233213287814244
34 ms 173.0.137.5
20 2026-08-26 06:02 639233202925983161
237 ms 173.0.137.5
19 2026-08-26 05:45 639233192644780696
239 ms 173.0.137.5
18 2026-08-26 05:28 639233182401183833
11 ms 173.0.137.5
17 2026-08-26 05:11 639233172074181051
240 ms 173.0.137.5
16 2026-08-26 04:54 639233161808421455
7 ms 173.0.137.5
15 2026-08-26 04:37 639233151357344052
2030 ms 173.0.137.5
14 2026-08-26 04:19 639233141034116946
366 ms 173.0.137.5
13 2026-08-26 04:02 639233130828334142
240 ms 173.0.137.5
12 2026-08-26 03:45 639233120373450007
2736 ms 173.0.137.5
11 2026-08-26 03:27 639233110066216193
239 ms 173.0.137.5
10 2026-08-26 02:34 639233078065410564
180 ms 173.0.137.5
9 2026-08-26 02:17 639233067787457832
277 ms 173.0.137.5
8 2026-08-26 02:00 639233057501801162
146 ms 173.0.137.5
7 2026-08-26 01:43 639233047089431703
2 ms 173.0.137.5
6 2026-08-26 01:25 639233036754790688
3 ms 173.0.137.5
5 2026-08-26 01:08 639233026412602472
243 ms 173.0.137.5
4 2026-08-26 00:51 639233016064066127
252 ms 173.0.137.5
3 2026-08-26 00:34 639233005922655772
242 ms 173.0.137.5
2 2026-08-26 00:17 639232995672256907
242 ms 173.0.137.5
1 2026-08-26 00:00 639232985300872416
240 ms 173.0.137.5