DNS response history for ns1.napervillefocuseyecare.com

ns1.napervillefocuseyecare.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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 461 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.napervillefocuseyecare.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

461 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.78.37.69

Most recently resolved hosting IP on selected date

Successful Responses

28

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.napervillefocuseyecare.com

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
28 2026-08-24 11:49 639231683712487276
2136 ms 166.78.37.69
27 2026-08-24 11:32 639231673513573868
4 ms 166.78.37.69
26 2026-08-24 10:39 639231641791249939
277 ms 166.78.37.69
25 2026-08-24 10:23 639231631866211033
566 ms 166.78.37.69
24 2026-08-24 10:06 639231621644955316
294 ms 166.78.37.69
23 2026-08-24 09:49 639231611478799259
552 ms 166.78.37.69
22 2026-08-24 08:56 639231579923718211
271 ms 166.78.37.69
21 2026-08-24 08:39 639231569810702936
272 ms 166.78.37.69
20 2026-08-24 08:22 639231559762411619
2135 ms 166.78.37.69
19 2026-08-24 08:06 639231549663595407
7 ms 166.78.37.69
18 2026-08-24 07:13 639231518076817246
277 ms 166.78.37.69
17 2026-08-24 06:57 639231508078650885
268 ms 166.78.37.69
16 2026-08-24 06:40 639231498210697093
271 ms 166.78.37.69
15 2026-08-24 06:23 639231488109699360
158 ms 166.78.37.69
14 2026-08-24 05:31 639231456772510692
126 ms 166.78.37.69
13 2026-08-24 05:15 639231447084631185
2 ms 166.78.37.69
12 2026-08-24 04:58 639231437208519473
2 ms 166.78.37.69
11 2026-08-24 04:42 639231427209627490
3 ms 166.78.37.69
10 2026-08-24 03:49 639231395791246644
2 ms 166.78.37.69
9 2026-08-24 03:33 639231386075551458
151 ms 166.78.37.69
8 2026-08-24 03:17 639231376208713791
182 ms 166.78.37.69
7 2026-08-24 03:00 639231366170589276
270 ms 166.78.37.69
6 2026-08-24 02:08 639231334732159368
7 ms 166.78.37.69
5 2026-08-24 01:51 639231325035670078
3 ms 166.78.37.69
4 2026-08-24 01:35 639231315132253837
400 ms 166.78.37.69
3 2026-08-24 01:18 639231305014280808
3 ms 166.78.37.69
2 2026-08-24 00:26 639231273779380675
2132 ms 166.78.37.69
1 2026-08-24 00:10 639231264180839154
2134 ms 166.78.37.69