DNS response history for ns2.autodat.org

ns2.autodat.org 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 38 DNS check records, 36 successful responses, 2 failed responses, and 246 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.autodat.org.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

168.119.141.87

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.autodat.org

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
38 2026-08-25 13:06 639232597643611557
27 ms 168.119.141.87
37 2026-08-25 12:49 639232587225721862
52 ms 168.119.141.87
36 2026-08-25 12:31 639232576780683689
532 ms 168.119.141.87
35 2026-08-25 12:14 639232566381512620
59 ms 168.119.141.87
34 2026-08-25 11:57 639232556111768563
34 ms 168.119.141.87
33 2026-08-25 11:40 639232545839529039
179 ms 168.119.141.87
32 2026-08-25 11:22 639232535349285207
182 ms 168.119.141.87
31 2026-08-25 11:05 639232524938080723
2178 ms 168.119.141.87
30 2026-08-25 10:11 639232492740373468
52 ms 168.119.141.87
29 2026-08-25 09:54 639232482235303141
167 ms 168.119.141.87
28 2026-08-25 09:36 639232471861770303
-
27 2026-08-25 09:19 639232461630217327
37 ms 168.119.141.87
26 2026-08-25 09:02 639232451282965990
2066 ms 168.119.141.87
25 2026-08-25 08:45 639232440814614938
53 ms 168.119.141.87
24 2026-08-25 08:27 639232430410720425
-
23 2026-08-25 08:10 639232420003096185
85 ms 168.119.141.87
22 2026-08-25 07:52 639232409467287444
158 ms 168.119.141.87
21 2026-08-25 07:35 639232399077195997
29 ms 168.119.141.87
20 2026-08-25 07:18 639232388731528337
95 ms 168.119.141.87
19 2026-08-25 07:00 639232378288598612
21 ms 168.119.141.87
18 2026-08-25 06:07 639232346196373643
36 ms 168.119.141.87
17 2026-08-25 05:50 639232336112370741
42 ms 168.119.141.87
16 2026-08-25 05:33 639232326146508970
82 ms 168.119.141.87
15 2026-08-25 05:17 639232316189381720
47 ms 168.119.141.87
14 2026-08-25 05:00 639232306217998913
59 ms 168.119.141.87
13 2026-08-25 04:44 639232296255744174
2023 ms 168.119.141.87
12 2026-08-25 04:27 639232286095760789
36 ms 168.119.141.87
11 2026-08-25 04:10 639232276086186273
31 ms 168.119.141.87
10 2026-08-25 03:53 639232265900986425
91 ms 168.119.141.87
9 2026-08-25 03:36 639232255723518075
14 ms 168.119.141.87
8 2026-08-25 03:19 639232245484452890
7 ms 168.119.141.87
7 2026-08-25 03:02 639232235157175331
54 ms 168.119.141.87
6 2026-08-25 02:09 639232203197189095
11 ms 168.119.141.87
5 2026-08-25 01:51 639232192844564298
70 ms 168.119.141.87
4 2026-08-25 01:34 639232182496008942
48 ms 168.119.141.87
3 2026-08-25 01:17 639232172197053132
94 ms 168.119.141.87
2 2026-08-25 00:24 639232140250307418
50 ms 168.119.141.87
1 2026-08-25 00:06 639232129927860324
47 ms 168.119.141.87