DNS response history for ns1.eye4future.com

ns1.eye4future.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 34 DNS check records, 34 successful responses, 0 failed responses, and 301 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.eye4future.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

301 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.116.229.200

Most recently resolved hosting IP on selected date

Successful Responses

34

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.eye4future.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
34 2026-08-24 14:05 639231765923559455
277 ms 66.116.229.200
33 2026-08-24 13:48 639231755868832964
134 ms 66.116.229.200
32 2026-08-24 13:31 639231745628278877
6 ms 66.116.229.200
31 2026-08-24 13:14 639231735407682062
2 ms 66.116.229.200
30 2026-08-24 12:21 639231703815441688
267 ms 66.116.229.200
29 2026-08-24 12:05 639231693747052549
265 ms 66.116.229.200
28 2026-08-24 11:48 639231683712487276
250 ms 66.116.229.200
27 2026-08-24 11:31 639231673513573868
281 ms 66.116.229.200
26 2026-08-24 10:38 639231641791249939
257 ms 66.116.229.200
25 2026-08-24 10:22 639231631866211033
129 ms 66.116.229.200
24 2026-08-24 10:05 639231621644955316
372 ms 66.116.229.200
23 2026-08-24 09:48 639231611478799259
123 ms 66.116.229.200
22 2026-08-24 08:55 639231579923718211
204 ms 66.116.229.200
21 2026-08-24 08:38 639231569810702936
6 ms 66.116.229.200
20 2026-08-24 08:21 639231559762411619
125 ms 66.116.229.200
19 2026-08-24 08:05 639231549663595407
258 ms 66.116.229.200
18 2026-08-24 07:12 639231518076817246
415 ms 66.116.229.200
17 2026-08-24 06:56 639231508078650885
267 ms 66.116.229.200
16 2026-08-24 06:39 639231498210697093
262 ms 66.116.229.200
15 2026-08-24 06:22 639231488109699360
2376 ms 66.116.229.200
14 2026-08-24 05:30 639231456772510692
48 ms 66.116.229.200
13 2026-08-24 05:14 639231447084631185
260 ms 66.116.229.200
12 2026-08-24 04:57 639231437208519473
250 ms 66.116.229.200
11 2026-08-24 04:41 639231427209627490
370 ms 66.116.229.200
10 2026-08-24 03:48 639231395791246644
12 ms 66.116.229.200
9 2026-08-24 03:32 639231386075551458
9 ms 66.116.229.200
8 2026-08-24 03:16 639231376208713791
248 ms 66.116.229.200
7 2026-08-24 02:59 639231366170589276
249 ms 66.116.229.200
6 2026-08-24 02:07 639231334732159368
9 ms 66.116.229.200
5 2026-08-24 01:50 639231325035670078
282 ms 66.116.229.200
4 2026-08-24 01:34 639231315132253837
2034 ms 66.116.229.200
3 2026-08-24 01:17 639231305014280808
20 ms 66.116.229.200
2 2026-08-24 00:25 639231273779380675
3 ms 66.116.229.200
1 2026-08-24 00:09 639231264180839154
160 ms 66.116.229.200