DNS response history for ns2.altovalley.com

ns2.altovalley.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 33 DNS check records, 33 successful responses, 0 failed responses, and 125 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.altovalley.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

125 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.220.79

Most recently resolved hosting IP on selected date

Successful Responses

33

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.altovalley.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
33 2026-08-24 13:48 639231755868832964
272 ms 67.225.220.79
32 2026-08-24 13:31 639231745628278877
7 ms 67.225.220.79
31 2026-08-24 13:14 639231735407682062
273 ms 67.225.220.79
30 2026-08-24 12:21 639231703815441688
13 ms 67.225.220.79
29 2026-08-24 12:05 639231693747052549
240 ms 67.225.220.79
28 2026-08-24 11:48 639231683712487276
27 ms 67.225.220.79
27 2026-08-24 11:31 639231673513573868
289 ms 67.225.220.79
26 2026-08-24 10:38 639231641791249939
18 ms 67.225.220.79
25 2026-08-24 10:21 639231631866211033
15 ms 67.225.220.79
24 2026-08-24 10:04 639231621644955316
257 ms 67.225.220.79
23 2026-08-24 09:47 639231611478799259
24 ms 67.225.220.79
22 2026-08-24 08:55 639231579923718211
311 ms 67.225.220.79
21 2026-08-24 08:38 639231569810702936
326 ms 67.225.220.79
20 2026-08-24 08:21 639231559762411619
5 ms 67.225.220.79
19 2026-08-24 08:04 639231549663595407
19 ms 67.225.220.79
18 2026-08-24 07:12 639231518076817246
24 ms 67.225.220.79
17 2026-08-24 06:55 639231508078650885
319 ms 67.225.220.79
16 2026-08-24 06:39 639231498210697093
33 ms 67.225.220.79
15 2026-08-24 06:22 639231488109699360
8 ms 67.225.220.79
14 2026-08-24 05:30 639231456772510692
343 ms 67.225.220.79
13 2026-08-24 05:14 639231447084631185
16 ms 67.225.220.79
12 2026-08-24 04:57 639231437208519473
9 ms 67.225.220.79
11 2026-08-24 04:40 639231427209627490
11 ms 67.225.220.79
10 2026-08-24 03:48 639231395791246644
298 ms 67.225.220.79
9 2026-08-24 03:32 639231386075551458
20 ms 67.225.220.79
8 2026-08-24 03:15 639231376208713791
30 ms 67.225.220.79
7 2026-08-24 02:59 639231366170589276
9 ms 67.225.220.79
6 2026-08-24 02:06 639231334732159368
294 ms 67.225.220.79
5 2026-08-24 01:50 639231325035670078
279 ms 67.225.220.79
4 2026-08-24 01:34 639231315132253837
297 ms 67.225.220.79
3 2026-08-24 01:17 639231305014280808
14 ms 67.225.220.79
2 2026-08-24 00:25 639231273779380675
16 ms 67.225.220.79
1 2026-08-24 00:09 639231264180839154
9 ms 67.225.220.79