DNS response history for ns1.avraread.com

ns1.avraread.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 256 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.avraread.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

256 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.74.95.229

Most recently resolved hosting IP on selected date

Successful Responses

35

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

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
35 2026-08-26 11:40 639233403515141099
313 ms 209.74.95.229
34 2026-08-26 10:46 639233370841350248
148 ms 209.74.95.229
33 2026-08-26 10:29 639233360361507238
144 ms 209.74.95.229
32 2026-08-26 10:11 639233350067824371
306 ms 209.74.95.229
31 2026-08-26 09:54 639233339545274518
312 ms 209.74.95.229
30 2026-08-26 09:36 639233329214918079
153 ms 209.74.95.229
29 2026-08-26 09:19 639233318749762337
146 ms 209.74.95.229
28 2026-08-26 09:02 639233308387917838
300 ms 209.74.95.229
27 2026-08-26 08:44 639233297961740122
292 ms 209.74.95.229
26 2026-08-26 08:27 639233287487159094
318 ms 209.74.95.229
25 2026-08-26 08:10 639233276995531707
297 ms 209.74.95.229
24 2026-08-26 07:52 639233266521568229
156 ms 209.74.95.229
23 2026-08-26 07:35 639233256081047431
297 ms 209.74.95.229
22 2026-08-26 06:41 639233223620132921
303 ms 209.74.95.229
21 2026-08-26 06:23 639233213287814244
302 ms 209.74.95.229
20 2026-08-26 06:06 639233202925983161
149 ms 209.74.95.229
19 2026-08-26 05:49 639233192644780696
163 ms 209.74.95.229
18 2026-08-26 05:32 639233182401183833
313 ms 209.74.95.229
17 2026-08-26 05:15 639233172074181051
300 ms 209.74.95.229
16 2026-08-26 04:57 639233161808421455
155 ms 209.74.95.229
15 2026-08-26 04:40 639233151357344052
306 ms 209.74.95.229
14 2026-08-26 04:23 639233141034116946
328 ms 209.74.95.229
13 2026-08-26 04:06 639233130828334142
291 ms 209.74.95.229
12 2026-08-26 03:48 639233120373450007
292 ms 209.74.95.229
11 2026-08-26 03:31 639233110066216193
149 ms 209.74.95.229
10 2026-08-26 02:38 639233078065410564
299 ms 209.74.95.229
9 2026-08-26 02:21 639233067787457832
298 ms 209.74.95.229
8 2026-08-26 02:04 639233057501801162
300 ms 209.74.95.229
7 2026-08-26 01:46 639233047089431703
158 ms 209.74.95.229
6 2026-08-26 01:29 639233036754790688
318 ms 209.74.95.229
5 2026-08-26 01:12 639233026412602472
312 ms 209.74.95.229
4 2026-08-26 00:54 639233016064066127
290 ms 209.74.95.229
3 2026-08-26 00:37 639233005922655772
307 ms 209.74.95.229
2 2026-08-26 00:20 639232995672256907
149 ms 209.74.95.229
1 2026-08-26 00:03 639232985300872416
298 ms 209.74.95.229