DNS response history for ns1.max2tally.com

ns1.max2tally.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 35 DNS check records, 35 successful responses, 0 failed responses, and 329 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.max2tally.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

329 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.156.20.111

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 ns1.max2tally.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
35 2026-08-25 12:21 639232566381512620
240 ms 103.156.20.111
34 2026-08-25 12:04 639232556111768563
265 ms 103.156.20.111
33 2026-08-25 11:47 639232545839529039
244 ms 103.156.20.111
32 2026-08-25 11:29 639232535349285207
267 ms 103.156.20.111
31 2026-08-25 11:12 639232524938080723
254 ms 103.156.20.111
30 2026-08-25 10:18 639232492740373468
126 ms 103.156.20.111
29 2026-08-25 10:01 639232482235303141
251 ms 103.156.20.111
28 2026-08-25 09:44 639232471861770303
153 ms 103.156.20.111
27 2026-08-25 09:26 639232461630217327
279 ms 103.156.20.111
26 2026-08-25 09:09 639232451282965990
135 ms 103.156.20.111
25 2026-08-25 08:52 639232440814614938
244 ms 103.156.20.111
24 2026-08-25 08:34 639232430410720425
241 ms 103.156.20.111
23 2026-08-25 08:17 639232420003096185
124 ms 103.156.20.111
22 2026-08-25 08:00 639232409467287444
267 ms 103.156.20.111
21 2026-08-25 07:42 639232399077195997
128 ms 103.156.20.111
20 2026-08-25 07:25 639232388731528337
144 ms 103.156.20.111
19 2026-08-25 07:08 639232378288598612
252 ms 103.156.20.111
18 2026-08-25 06:14 639232346196373643
127 ms 103.156.20.111
17 2026-08-25 05:57 639232336112370741
242 ms 103.156.20.111
16 2026-08-25 05:40 639232326146508970
146 ms 103.156.20.111
15 2026-08-25 05:24 639232316189381720
2183 ms 103.156.20.111
14 2026-08-25 05:07 639232306217998913
243 ms 103.156.20.111
13 2026-08-25 04:51 639232296255744174
259 ms 103.156.20.111
12 2026-08-25 04:34 639232286095760789
243 ms 103.156.20.111
11 2026-08-25 04:17 639232276086186273
146 ms 103.156.20.111
10 2026-08-25 04:00 639232265900986425
157 ms 103.156.20.111
9 2026-08-25 03:43 639232255723518075
237 ms 103.156.20.111
8 2026-08-25 03:26 639232245484452890
242 ms 103.156.20.111
7 2026-08-25 03:09 639232235157175331
120 ms 103.156.20.111
6 2026-08-25 02:16 639232203197189095
2381 ms 103.156.20.111
5 2026-08-25 01:59 639232192844564298
242 ms 103.156.20.111
4 2026-08-25 01:41 639232182496008942
161 ms 103.156.20.111
3 2026-08-25 01:24 639232172197053132
245 ms 103.156.20.111
2 2026-08-25 00:31 639232140250307418
241 ms 103.156.20.111
1 2026-08-25 00:14 639232129927860324
273 ms 103.156.20.111