DNS response history for ns2.maxdocument.com

ns2.maxdocument.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 476 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 ns2.maxdocument.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

476 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.50.77.102

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns2.maxdocument.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:12 639234253963286387
305 ms 49.50.77.102
34 2026-08-27 10:55 639234243654907465
305 ms 49.50.77.102
33 2026-08-27 10:37 639234233269654413
5 ms 49.50.77.102
32 2026-08-27 10:20 639234222943951923
306 ms 49.50.77.102
31 2026-08-27 10:03 639234212558002823
7 ms 49.50.77.102
30 2026-08-27 09:45 639234202117531850
5 ms 49.50.77.102
29 2026-08-27 09:28 639234191649612722
325 ms 49.50.77.102
28 2026-08-27 09:10 639234181105879568
304 ms 49.50.77.102
27 2026-08-27 08:53 639234170713214496
292 ms 49.50.77.102
26 2026-08-27 08:36 639234160341037652
312 ms 49.50.77.102
25 2026-08-27 08:18 639234149799404224
304 ms 49.50.77.102
24 2026-08-27 08:01 639234139553286469
308 ms 49.50.77.102
23 2026-08-27 07:07 639234107183588293
4176 ms 49.50.77.102
22 2026-08-27 06:50 639234096905435724
304 ms 49.50.77.102
21 2026-08-27 06:33 639234086579410775
301 ms 49.50.77.102
20 2026-08-27 06:16 639234076291157956
312 ms 49.50.77.102
19 2026-08-27 05:59 639234065981939454
298 ms 49.50.77.102
18 2026-08-27 05:41 639234055548642997
163 ms 49.50.77.102
17 2026-08-27 05:24 639234045267979603
243 ms 49.50.77.102
16 2026-08-27 05:07 639234034999717463
2382 ms 49.50.77.102
15 2026-08-27 04:50 639234024739225358
302 ms 49.50.77.102
14 2026-08-27 04:33 639234014311170162
294 ms 49.50.77.102
13 2026-08-27 04:15 639234003806017640
327 ms 49.50.77.102
12 2026-08-27 03:58 639233993356203030
336 ms 49.50.77.102
11 2026-08-27 03:04 639233961301716608
313 ms 49.50.77.102
10 2026-08-27 02:47 639233950834200647
175 ms 49.50.77.102
9 2026-08-27 02:29 639233940431849026
7 ms 49.50.77.102
8 2026-08-27 02:12 639233930110596398
2031 ms 49.50.77.102
7 2026-08-27 01:55 639233919705434540
303 ms 49.50.77.102
6 2026-08-27 01:38 639233909452807845
317 ms 49.50.77.102
5 2026-08-27 01:20 639233899096420820
27 ms 49.50.77.102
4 2026-08-27 01:03 639233888707824939
319 ms 49.50.77.102
3 2026-08-27 00:46 639233878461203802
312 ms 49.50.77.102
2 2026-08-27 00:29 639233868060868209
312 ms 49.50.77.102
1 2026-08-27 00:11 639233857450922991
338 ms 49.50.77.102