DNS response history for dns2.26max.com

dns2.26max.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 442 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 dns2.26max.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

442 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.254.209.99

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 dns2.26max.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:16 639234253963286387
279 ms 162.254.209.99
34 2026-08-27 10:59 639234243654907465
271 ms 162.254.209.99
33 2026-08-27 10:42 639234233269654413
133 ms 162.254.209.99
32 2026-08-27 10:24 639234222943951923
267 ms 162.254.209.99
31 2026-08-27 10:07 639234212558002823
4 ms 162.254.209.99
30 2026-08-27 09:50 639234202117531850
145 ms 162.254.209.99
29 2026-08-27 09:32 639234191649612722
1155 ms 162.254.209.99
28 2026-08-27 09:15 639234181105879568
136 ms 162.254.209.99
27 2026-08-27 08:57 639234170713214496
133 ms 162.254.209.99
26 2026-08-27 08:40 639234160341037652
267 ms 162.254.209.99
25 2026-08-27 08:23 639234149799404224
135 ms 162.254.209.99
24 2026-08-27 08:05 639234139553286469
264 ms 162.254.209.99
23 2026-08-27 07:11 639234107183588293
269 ms 162.254.209.99
22 2026-08-27 06:54 639234096905435724
3631 ms 162.254.209.99
21 2026-08-27 06:37 639234086579410775
128 ms 162.254.209.99
20 2026-08-27 06:20 639234076291157956
257 ms 162.254.209.99
19 2026-08-27 06:03 639234065981939454
137 ms 162.254.209.99
18 2026-08-27 05:46 639234055548642997
131 ms 162.254.209.99
17 2026-08-27 05:28 639234045267979603
3 ms 162.254.209.99
16 2026-08-27 05:11 639234034999717463
4 ms 162.254.209.99
15 2026-08-27 04:54 639234024739225358
133 ms 162.254.209.99
14 2026-08-27 04:37 639234014311170162
267 ms 162.254.209.99
13 2026-08-27 04:19 639234003806017640
131 ms 162.254.209.99
12 2026-08-27 04:02 639233993356203030
137 ms 162.254.209.99
11 2026-08-27 03:08 639233961301716608
265 ms 162.254.209.99
10 2026-08-27 02:51 639233950834200647
132 ms 162.254.209.99
9 2026-08-27 02:34 639233940431849026
5135 ms 162.254.209.99
8 2026-08-27 02:16 639233930110596398
268 ms 162.254.209.99
7 2026-08-27 01:59 639233919705434540
141 ms 162.254.209.99
6 2026-08-27 01:42 639233909452807845
130 ms 162.254.209.99
5 2026-08-27 01:25 639233899096420820
273 ms 162.254.209.99
4 2026-08-27 01:07 639233888707824939
129 ms 162.254.209.99
3 2026-08-27 00:50 639233878461203802
189 ms 162.254.209.99
2 2026-08-27 00:33 639233868060868209
135 ms 162.254.209.99
1 2026-08-27 00:16 639233857450922991
265 ms 162.254.209.99