DNS response history for ns1.max-p.me

ns1.max-p.me 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 38 DNS check records, 38 successful responses, 0 failed responses, and 697 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.max-p.me.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

697 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.114.206.90

Most recently resolved hosting IP on selected date

Successful Responses

38

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.max-p.me

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
38 2026-08-25 13:16 639232597643611557
1617 ms 167.114.206.90
37 2026-08-25 12:58 639232587225721862
2233 ms 167.114.206.90
36 2026-08-25 12:41 639232576780683689
234 ms 167.114.206.90
35 2026-08-25 12:24 639232566381512620
3607 ms 167.114.206.90
34 2026-08-25 12:06 639232556111768563
223 ms 167.114.206.90
33 2026-08-25 11:49 639232545839529039
231 ms 167.114.206.90
32 2026-08-25 11:32 639232535349285207
1713 ms 167.114.206.90
31 2026-08-25 11:14 639232524938080723
342 ms 167.114.206.90
30 2026-08-25 10:21 639232492740373468
229 ms 167.114.206.90
29 2026-08-25 10:04 639232482235303141
232 ms 167.114.206.90
28 2026-08-25 09:46 639232471861770303
221 ms 167.114.206.90
27 2026-08-25 09:29 639232461630217327
3684 ms 167.114.206.90
26 2026-08-25 09:12 639232451282965990
108 ms 167.114.206.90
25 2026-08-25 08:54 639232440814614938
2222 ms 167.114.206.90
24 2026-08-25 08:37 639232430410720425
230 ms 167.114.206.90
23 2026-08-25 08:20 639232420003096185
226 ms 167.114.206.90
22 2026-08-25 08:02 639232409467287444
225 ms 167.114.206.90
21 2026-08-25 07:45 639232399077195997
899 ms 167.114.206.90
20 2026-08-25 07:27 639232388731528337
225 ms 167.114.206.90
19 2026-08-25 07:10 639232378288598612
1717 ms 167.114.206.90
18 2026-08-25 06:16 639232346196373643
223 ms 167.114.206.90
17 2026-08-25 06:00 639232336112370741
150 ms 167.114.206.90
16 2026-08-25 05:43 639232326146508970
1604 ms 167.114.206.90
15 2026-08-25 05:26 639232316189381720
13 ms 167.114.206.90
14 2026-08-25 05:10 639232306217998913
230 ms 167.114.206.90
13 2026-08-25 04:53 639232296255744174
1704 ms 167.114.206.90
12 2026-08-25 04:36 639232286095760789
4 ms 167.114.206.90
11 2026-08-25 04:19 639232276086186273
108 ms 167.114.206.90
10 2026-08-25 04:03 639232265900986425
220 ms 167.114.206.90
9 2026-08-25 03:46 639232255723518075
224 ms 167.114.206.90
8 2026-08-25 03:29 639232245484452890
228 ms 167.114.206.90
7 2026-08-25 03:12 639232235157175331
228 ms 167.114.206.90
6 2026-08-25 02:18 639232203197189095
233 ms 167.114.206.90
5 2026-08-25 02:01 639232192844564298
222 ms 167.114.206.90
4 2026-08-25 01:44 639232182496008942
230 ms 167.114.206.90
3 2026-08-25 01:26 639232172197053132
2 ms 167.114.206.90
2 2026-08-25 00:33 639232140250307418
221 ms 167.114.206.90
1 2026-08-25 00:16 639232129927860324
231 ms 167.114.206.90