DNS response history for ns1.maximweb.com

ns1.maximweb.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 290 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 ns1.maximweb.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.152.220.79

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns1.maximweb.com

Showing DNS history for 2026-08-25 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
36 2026-08-25 12:33 639232576780683689
122 ms 66.152.220.79
35 2026-08-25 12:16 639232566381512620
128 ms 66.152.220.79
34 2026-08-25 11:59 639232556111768563
131 ms 66.152.220.79
33 2026-08-25 11:42 639232545839529039
19 ms 66.152.220.79
32 2026-08-25 11:24 639232535349285207
150 ms 66.152.220.79
31 2026-08-25 11:07 639232524938080723
2131 ms 66.152.220.79
30 2026-08-25 10:13 639232492740373468
163 ms 66.152.220.79
29 2026-08-25 09:56 639232482235303141
131 ms 66.152.220.79
28 2026-08-25 09:38 639232471861770303
152 ms 66.152.220.79
27 2026-08-25 09:21 639232461630217327
148 ms 66.152.220.79
26 2026-08-25 09:04 639232451282965990
124 ms 66.152.220.79
25 2026-08-25 08:47 639232440814614938
130 ms 66.152.220.79
24 2026-08-25 08:29 639232430410720425
214 ms 66.152.220.79
23 2026-08-25 08:12 639232420003096185
154 ms 66.152.220.79
22 2026-08-25 07:54 639232409467287444
137 ms 66.152.220.79
21 2026-08-25 07:37 639232399077195997
2015 ms 66.152.220.79
20 2026-08-25 07:20 639232388731528337
121 ms 66.152.220.79
19 2026-08-25 07:02 639232378288598612
148 ms 66.152.220.79
18 2026-08-25 06:09 639232346196373643
129 ms 66.152.220.79
17 2026-08-25 05:52 639232336112370741
127 ms 66.152.220.79
16 2026-08-25 05:35 639232326146508970
141 ms 66.152.220.79
15 2026-08-25 05:19 639232316189381720
123 ms 66.152.220.79
14 2026-08-25 05:02 639232306217998913
127 ms 66.152.220.79
13 2026-08-25 04:46 639232296255744174
127 ms 66.152.220.79
12 2026-08-25 04:29 639232286095760789
120 ms 66.152.220.79
11 2026-08-25 04:12 639232276086186273
43 ms 66.152.220.79
10 2026-08-25 03:55 639232265900986425
121 ms 66.152.220.79
9 2026-08-25 03:38 639232255723518075
123 ms 66.152.220.79
8 2026-08-25 03:21 639232245484452890
118 ms 66.152.220.79
7 2026-08-25 03:04 639232235157175331
123 ms 66.152.220.79
6 2026-08-25 02:11 639232203197189095
27 ms 66.152.220.79
5 2026-08-25 01:53 639232192844564298
132 ms 66.152.220.79
4 2026-08-25 01:36 639232182496008942
134 ms 66.152.220.79
3 2026-08-25 01:19 639232172197053132
129 ms 66.152.220.79
2 2026-08-25 00:26 639232140250307418
2147 ms 66.152.220.79
1 2026-08-25 00:08 639232129927860324
126 ms 66.152.220.79