DNS response history for ns2.aventurevelo.com

ns2.aventurevelo.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 316 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.aventurevelo.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

316 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.30.177

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

Showing DNS history for 2026-08-25 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-25 12:35 639232576780683689
221 ms 51.222.30.177
35 2026-08-25 12:17 639232566381512620
107 ms 51.222.30.177
34 2026-08-25 12:00 639232556111768563
242 ms 51.222.30.177
33 2026-08-25 11:43 639232545839529039
219 ms 51.222.30.177
32 2026-08-25 11:26 639232535349285207
222 ms 51.222.30.177
31 2026-08-25 11:08 639232524938080723
222 ms 51.222.30.177
30 2026-08-25 10:15 639232492740373468
224 ms 51.222.30.177
29 2026-08-25 09:57 639232482235303141
7 ms 51.222.30.177
28 2026-08-25 09:40 639232471861770303
7 ms 51.222.30.177
27 2026-08-25 09:23 639232461630217327
110 ms 51.222.30.177
26 2026-08-25 09:06 639232451282965990
222 ms 51.222.30.177
25 2026-08-25 08:48 639232440814614938
221 ms 51.222.30.177
24 2026-08-25 08:31 639232430410720425
229 ms 51.222.30.177
23 2026-08-25 08:14 639232420003096185
12 ms 51.222.30.177
22 2026-08-25 07:56 639232409467287444
236 ms 51.222.30.177
21 2026-08-25 07:39 639232399077195997
217 ms 51.222.30.177
20 2026-08-25 07:21 639232388731528337
128 ms 51.222.30.177
19 2026-08-25 07:04 639232378288598612
2230 ms 51.222.30.177
18 2026-08-25 06:10 639232346196373643
220 ms 51.222.30.177
17 2026-08-25 05:54 639232336112370741
110 ms 51.222.30.177
16 2026-08-25 05:37 639232326146508970
221 ms 51.222.30.177
15 2026-08-25 05:20 639232316189381720
104 ms 51.222.30.177
14 2026-08-25 05:04 639232306217998913
123 ms 51.222.30.177
13 2026-08-25 04:47 639232296255744174
104 ms 51.222.30.177
12 2026-08-25 04:30 639232286095760789
3 ms 51.222.30.177
11 2026-08-25 04:13 639232276086186273
224 ms 51.222.30.177
10 2026-08-25 03:57 639232265900986425
230 ms 51.222.30.177
9 2026-08-25 03:40 639232255723518075
14 ms 51.222.30.177
8 2026-08-25 03:23 639232245484452890
219 ms 51.222.30.177
7 2026-08-25 03:05 639232235157175331
2134 ms 51.222.30.177
6 2026-08-25 02:12 639232203197189095
222 ms 51.222.30.177
5 2026-08-25 01:55 639232192844564298
230 ms 51.222.30.177
4 2026-08-25 01:38 639232182496008942
7 ms 51.222.30.177
3 2026-08-25 01:20 639232172197053132
2010 ms 51.222.30.177
2 2026-08-25 00:27 639232140250307418
7 ms 51.222.30.177
1 2026-08-25 00:10 639232129927860324
119 ms 51.222.30.177