DNS response history for ns2.maxbot.com

ns2.maxbot.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 37 DNS check records, 37 successful responses, 0 failed responses, and 238 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.maxbot.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

238 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.161.36.41

Most recently resolved hosting IP on selected date

Successful Responses

37

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.maxbot.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
37 2026-08-27 12:19 639234296664302575
27 ms 209.161.36.41
36 2026-08-27 12:02 639234286253196126
29 ms 209.161.36.41
35 2026-08-27 11:08 639234253963286387
31 ms 209.161.36.41
34 2026-08-27 10:51 639234243654907465
10 ms 209.161.36.41
33 2026-08-27 10:34 639234233269654413
19 ms 209.161.36.41
32 2026-08-27 10:17 639234222943951923
2012 ms 209.161.36.41
31 2026-08-27 09:59 639234212558002823
50 ms 209.161.36.41
30 2026-08-27 09:42 639234202117531850
36 ms 209.161.36.41
29 2026-08-27 09:24 639234191649612722
14 ms 209.161.36.41
28 2026-08-27 09:07 639234181105879568
20 ms 209.161.36.41
27 2026-08-27 08:50 639234170713214496
28 ms 209.161.36.41
26 2026-08-27 08:32 639234160341037652
35 ms 209.161.36.41
25 2026-08-27 08:15 639234149799404224
12 ms 209.161.36.41
24 2026-08-27 07:58 639234139553286469
16 ms 209.161.36.41
23 2026-08-27 07:04 639234107183588293
7 ms 209.161.36.41
22 2026-08-27 06:47 639234096905435724
5 ms 209.161.36.41
21 2026-08-27 06:30 639234086579410775
33 ms 209.161.36.41
20 2026-08-27 06:12 639234076291157956
19 ms 209.161.36.41
19 2026-08-27 05:55 639234065981939454
11 ms 209.161.36.41
18 2026-08-27 05:38 639234055548642997
14 ms 209.161.36.41
17 2026-08-27 05:20 639234045267979603
21 ms 209.161.36.41
16 2026-08-27 05:04 639234034999717463
18 ms 209.161.36.41
15 2026-08-27 04:46 639234024739225358
57 ms 209.161.36.41
14 2026-08-27 04:29 639234014311170162
2023 ms 209.161.36.41
13 2026-08-27 04:11 639234003806017640
6 ms 209.161.36.41
12 2026-08-27 03:54 639233993356203030
22 ms 209.161.36.41
11 2026-08-27 03:01 639233961301716608
37 ms 209.161.36.41
10 2026-08-27 02:43 639233950834200647
4 ms 209.161.36.41
9 2026-08-27 02:26 639233940431849026
32 ms 209.161.36.41
8 2026-08-27 02:09 639233930110596398
24 ms 209.161.36.41
7 2026-08-27 01:51 639233919705434540
14 ms 209.161.36.41
6 2026-08-27 01:34 639233909452807845
2016 ms 209.161.36.41
5 2026-08-27 01:17 639233899096420820
22 ms 209.161.36.41
4 2026-08-27 01:00 639233888707824939
12 ms 209.161.36.41
3 2026-08-27 00:43 639233878461203802
13 ms 209.161.36.41
2 2026-08-27 00:25 639233868060868209
10 ms 209.161.36.41
1 2026-08-27 00:08 639233857450922991
2035 ms 209.161.36.41