DNS response history for ns2.mil.autos

ns2.mil.autos 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-24. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 467 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.mil.autos.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

467 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.168.248.132

Most recently resolved hosting IP on selected date

Successful Responses

31

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.mil.autos

Showing DNS history for 2026-08-24 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
31 2026-08-24 13:17 639231735407682062
336 ms 104.168.248.132
30 2026-08-24 12:24 639231703815441688
5 ms 104.168.248.132
29 2026-08-24 12:08 639231693747052549
348 ms 104.168.248.132
28 2026-08-24 11:51 639231683712487276
33 ms 104.168.248.132
27 2026-08-24 11:34 639231673513573868
2149 ms 104.168.248.132
26 2026-08-24 10:41 639231641791249939
330 ms 104.168.248.132
25 2026-08-24 10:25 639231631866211033
362 ms 104.168.248.132
24 2026-08-24 10:08 639231621644955316
381 ms 104.168.248.132
23 2026-08-24 09:51 639231611478799259
364 ms 104.168.248.132
22 2026-08-24 08:58 639231579923718211
330 ms 104.168.248.132
21 2026-08-24 08:41 639231569810702936
341 ms 104.168.248.132
20 2026-08-24 08:24 639231559762411619
225 ms 104.168.248.132
19 2026-08-24 08:08 639231549663595407
361 ms 104.168.248.132
18 2026-08-24 07:15 639231518076817246
373 ms 104.168.248.132
17 2026-08-24 06:59 639231508078650885
9 ms 104.168.248.132
16 2026-08-24 06:42 639231498210697093
186 ms 104.168.248.132
15 2026-08-24 06:25 639231488109699360
2009 ms 104.168.248.132
14 2026-08-24 05:33 639231456772510692
362 ms 104.168.248.132
13 2026-08-24 05:17 639231447084631185
377 ms 104.168.248.132
12 2026-08-24 05:00 639231437208519473
387 ms 104.168.248.132
11 2026-08-24 04:43 639231427209627490
3 ms 104.168.248.132
10 2026-08-24 03:51 639231395791246644
2162 ms 104.168.248.132
9 2026-08-24 03:35 639231386075551458
328 ms 104.168.248.132
8 2026-08-24 03:19 639231376208713791
176 ms 104.168.248.132
7 2026-08-24 03:02 639231366170589276
162 ms 104.168.248.132
6 2026-08-24 02:09 639231334732159368
3 ms 104.168.248.132
5 2026-08-24 01:53 639231325035670078
2 ms 104.168.248.132
4 2026-08-24 01:37 639231315132253837
2 ms 104.168.248.132
3 2026-08-24 01:20 639231305014280808
2352 ms 104.168.248.132
2 2026-08-24 00:28 639231273779380675
4 ms 104.168.248.132
1 2026-08-24 00:12 639231264180839154
3 ms 104.168.248.132