DNS response history for ns111.1maxhosting.com

ns111.1maxhosting.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, 31 successful responses, 2 failed responses, and 83 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 ns111.1maxhosting.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

83 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

43.225.108.235

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns111.1maxhosting.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
34 ms 43.225.108.235
32 2026-08-26 10:14 639233360361507238
-
31 2026-08-26 09:56 639233350067824371
63 ms 43.225.108.235
30 2026-08-26 09:39 639233339545274518
31 ms 43.225.108.235
29 2026-08-26 09:22 639233329214918079
58 ms 43.225.108.235
28 2026-08-26 09:04 639233318749762337
23 ms 43.225.108.235
27 2026-08-26 08:47 639233308387917838
6 ms 43.225.108.235
26 2026-08-26 08:29 639233297961740122
36 ms 43.225.108.235
25 2026-08-26 08:12 639233287487159094
24 ms 43.225.108.235
24 2026-08-26 07:54 639233276995531707
29 ms 43.225.108.235
23 2026-08-26 07:37 639233266521568229
56 ms 43.225.108.235
22 2026-08-26 07:20 639233256081047431
353 ms 43.225.108.235
21 2026-08-26 06:26 639233223620132921
-
20 2026-08-26 06:08 639233213287814244
33 ms 43.225.108.235
19 2026-08-26 05:51 639233202925983161
229 ms 43.225.108.235
18 2026-08-26 05:34 639233192644780696
69 ms 43.225.108.235
17 2026-08-26 05:17 639233182401183833
38 ms 43.225.108.235
16 2026-08-26 05:00 639233172074181051
40 ms 43.225.108.235
15 2026-08-26 04:43 639233161808421455
149 ms 43.225.108.235
14 2026-08-26 04:25 639233151357344052
42 ms 43.225.108.235
13 2026-08-26 04:08 639233141034116946
14 ms 43.225.108.235
12 2026-08-26 03:51 639233130828334142
33 ms 43.225.108.235
11 2026-08-26 03:33 639233120373450007
208 ms 43.225.108.235
10 2026-08-26 03:16 639233110066216193
494 ms 43.225.108.235
9 2026-08-26 02:23 639233078065410564
40 ms 43.225.108.235
8 2026-08-26 02:06 639233067787457832
28 ms 43.225.108.235
7 2026-08-26 01:49 639233057501801162
47 ms 43.225.108.235
6 2026-08-26 01:31 639233047089431703
17 ms 43.225.108.235
5 2026-08-26 01:14 639233036754790688
255 ms 43.225.108.235
4 2026-08-26 00:57 639233026412602472
21 ms 43.225.108.235
3 2026-08-26 00:40 639233016064066127
52 ms 43.225.108.235
2 2026-08-26 00:23 639233005922655772
34 ms 43.225.108.235
1 2026-08-26 00:06 639232995672256907
15 ms 43.225.108.235