DNS response history for ns1.dryeyes.tech

ns1.dryeyes.tech 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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 424 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.dryeyes.tech.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

424 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.66.126.144

Most recently resolved hosting IP on selected date

Successful Responses

38

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.dryeyes.tech

Showing DNS history for 2026-08-26 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-26 12:45 639233445367152284
4 ms 34.66.126.144
37 2026-08-26 12:27 639233434974187439
4 ms 34.66.126.144
36 2026-08-26 12:10 639233424567558554
268 ms 34.66.126.144
35 2026-08-26 11:53 639233414056832719
274 ms 34.66.126.144
34 2026-08-26 11:35 639233403515141099
271 ms 34.66.126.144
33 2026-08-26 10:40 639233370841350248
271 ms 34.66.126.144
32 2026-08-26 10:23 639233360361507238
175 ms 34.66.126.144
31 2026-08-26 10:06 639233350067824371
272 ms 34.66.126.144
30 2026-08-26 09:49 639233339545274518
132 ms 34.66.126.144
29 2026-08-26 09:31 639233329214918079
261 ms 34.66.126.144
28 2026-08-26 09:14 639233318749762337
275 ms 34.66.126.144
27 2026-08-26 08:56 639233308387917838
183 ms 34.66.126.144
26 2026-08-26 08:39 639233297961740122
269 ms 34.66.126.144
25 2026-08-26 08:22 639233287487159094
274 ms 34.66.126.144
24 2026-08-26 08:04 639233276995531707
274 ms 34.66.126.144
23 2026-08-26 07:47 639233266521568229
283 ms 34.66.126.144
22 2026-08-26 07:29 639233256081047431
265 ms 34.66.126.144
21 2026-08-26 06:35 639233223620132921
265 ms 34.66.126.144
20 2026-08-26 06:18 639233213287814244
265 ms 34.66.126.144
19 2026-08-26 06:01 639233202925983161
275 ms 34.66.126.144
18 2026-08-26 05:43 639233192644780696
2128 ms 34.66.126.144
17 2026-08-26 05:26 639233182401183833
263 ms 34.66.126.144
16 2026-08-26 05:09 639233172074181051
178 ms 34.66.126.144
15 2026-08-26 04:52 639233161808421455
276 ms 34.66.126.144
14 2026-08-26 04:35 639233151357344052
281 ms 34.66.126.144
13 2026-08-26 04:17 639233141034116946
268 ms 34.66.126.144
12 2026-08-26 04:00 639233130828334142
274 ms 34.66.126.144
11 2026-08-26 03:43 639233120373450007
276 ms 34.66.126.144
10 2026-08-26 03:26 639233110066216193
10 ms 34.66.126.144
9 2026-08-26 02:32 639233078065410564
266 ms 34.66.126.144
8 2026-08-26 02:15 639233067787457832
138 ms 34.66.126.144
7 2026-08-26 01:58 639233057501801162
266 ms 34.66.126.144
6 2026-08-26 01:41 639233047089431703
272 ms 34.66.126.144
5 2026-08-26 01:24 639233036754790688
8 ms 34.66.126.144
4 2026-08-26 01:06 639233026412602472
272 ms 34.66.126.144
3 2026-08-26 00:49 639233016064066127
4122 ms 34.66.126.144
2 2026-08-26 00:32 639233005922655772
137 ms 34.66.126.144
1 2026-08-26 00:15 639232995672256907
2128 ms 34.66.126.144