DNS response history for ns2.autos506.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

194 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.0.225.123

Most recently resolved hosting IP on selected date

Successful Responses

36

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.autos506.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
36 2026-08-25 12:25 639232566381512620
310 ms 162.0.225.123
35 2026-08-25 12:08 639232556111768563
308 ms 162.0.225.123
34 2026-08-25 11:51 639232545839529039
151 ms 162.0.225.123
33 2026-08-25 11:34 639232535349285207
323 ms 162.0.225.123
32 2026-08-25 11:16 639232524938080723
3 ms 162.0.225.123
31 2026-08-25 10:22 639232492740373468
143 ms 162.0.225.123
30 2026-08-25 10:05 639232482235303141
142 ms 162.0.225.123
29 2026-08-25 09:48 639232471861770303
3 ms 162.0.225.123
28 2026-08-25 09:30 639232461630217327
4 ms 162.0.225.123
27 2026-08-25 09:13 639232451282965990
309 ms 162.0.225.123
26 2026-08-25 08:56 639232440814614938
34 ms 162.0.225.123
25 2026-08-25 08:39 639232430410720425
166 ms 162.0.225.123
24 2026-08-25 08:21 639232420003096185
314 ms 162.0.225.123
23 2026-08-25 08:04 639232409467287444
311 ms 162.0.225.123
22 2026-08-25 07:46 639232399077195997
313 ms 162.0.225.123
21 2026-08-25 07:29 639232388731528337
5 ms 162.0.225.123
20 2026-08-25 07:12 639232378288598612
215 ms 162.0.225.123
19 2026-08-25 06:18 639232346196373643
3 ms 162.0.225.123
18 2026-08-25 06:01 639232336112370741
17 ms 162.0.225.123
17 2026-08-25 05:44 639232326146508970
4 ms 162.0.225.123
16 2026-08-25 05:28 639232316189381720
322 ms 162.0.225.123
15 2026-08-25 05:11 639232306217998913
300 ms 162.0.225.123
14 2026-08-25 04:54 639232296255744174
3 ms 162.0.225.123
13 2026-08-25 04:38 639232286095760789
319 ms 162.0.225.123
12 2026-08-25 04:21 639232276086186273
314 ms 162.0.225.123
11 2026-08-25 04:04 639232265900986425
151 ms 162.0.225.123
10 2026-08-25 03:47 639232255723518075
316 ms 162.0.225.123
9 2026-08-25 03:30 639232245484452890
306 ms 162.0.225.123
8 2026-08-25 03:13 639232235157175331
306 ms 162.0.225.123
7 2026-08-25 02:20 639232203197189095
319 ms 162.0.225.123
6 2026-08-25 02:03 639232192844564298
161 ms 162.0.225.123
5 2026-08-25 01:45 639232182496008942
319 ms 162.0.225.123
4 2026-08-25 01:28 639232172197053132
303 ms 162.0.225.123
3 2026-08-25 00:34 639232140250307418
311 ms 162.0.225.123
2 2026-08-25 00:18 639232129927860324
3 ms 162.0.225.123
1 2026-08-25 00:00 639232119551972438
148 ms 162.0.225.123