DNS response history for ns2.milesdeweb.us

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

36

Historical checks stored for this nameserver on selected date

Average Latency

266 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.91.198.102

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.milesdeweb.us

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
36 2026-08-24 15:17 639231807961539652
308 ms 208.91.198.102
35 2026-08-24 15:00 639231797631669865
143 ms 208.91.198.102
34 2026-08-24 14:07 639231765923559455
299 ms 208.91.198.102
33 2026-08-24 13:50 639231755868832964
314 ms 208.91.198.102
32 2026-08-24 13:33 639231745628278877
310 ms 208.91.198.102
31 2026-08-24 13:16 639231735407682062
313 ms 208.91.198.102
30 2026-08-24 12:23 639231703815441688
223 ms 208.91.198.102
29 2026-08-24 12:07 639231693747052549
311 ms 208.91.198.102
28 2026-08-24 11:50 639231683712487276
329 ms 208.91.198.102
27 2026-08-24 11:33 639231673513573868
310 ms 208.91.198.102
26 2026-08-24 10:40 639231641791249939
317 ms 208.91.198.102
25 2026-08-24 10:23 639231631866211033
170 ms 208.91.198.102
24 2026-08-24 10:06 639231621644955316
155 ms 208.91.198.102
23 2026-08-24 09:49 639231611478799259
147 ms 208.91.198.102
22 2026-08-24 08:57 639231579923718211
320 ms 208.91.198.102
21 2026-08-24 08:40 639231569810702936
306 ms 208.91.198.102
20 2026-08-24 08:23 639231559762411619
296 ms 208.91.198.102
19 2026-08-24 08:06 639231549663595407
142 ms 208.91.198.102
18 2026-08-24 07:14 639231518076817246
37 ms 208.91.198.102
17 2026-08-24 06:57 639231508078650885
228 ms 208.91.198.102
16 2026-08-24 06:41 639231498210697093
305 ms 208.91.198.102
15 2026-08-24 06:24 639231488109699360
7 ms 208.91.198.102
14 2026-08-24 05:32 639231456772510692
305 ms 208.91.198.102
13 2026-08-24 05:15 639231447084631185
305 ms 208.91.198.102
12 2026-08-24 04:59 639231437208519473
8 ms 208.91.198.102
11 2026-08-24 04:42 639231427209627490
13 ms 208.91.198.102
10 2026-08-24 03:50 639231395791246644
303 ms 208.91.198.102
9 2026-08-24 03:34 639231386075551458
145 ms 208.91.198.102
8 2026-08-24 03:17 639231376208713791
2145 ms 208.91.198.102
7 2026-08-24 03:01 639231366170589276
7 ms 208.91.198.102
6 2026-08-24 02:08 639231334732159368
309 ms 208.91.198.102
5 2026-08-24 01:52 639231325035670078
143 ms 208.91.198.102
4 2026-08-24 01:35 639231315132253837
144 ms 208.91.198.102
3 2026-08-24 01:19 639231305014280808
308 ms 208.91.198.102
2 2026-08-24 00:26 639231273779380675
164 ms 208.91.198.102
1 2026-08-24 00:11 639231264180839154
4 ms 208.91.198.102