DNS response history for ns2.vrocket.systems

ns2.vrocket.systems 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 32 DNS check records, 32 successful responses, 0 failed responses, and 289 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.vrocket.systems.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

289 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.144.29.9

Most recently resolved hosting IP on selected date

Successful Responses

32

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.vrocket.systems

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
32 2026-08-24 13:26 639231745628278877
26 ms 52.144.29.9
31 2026-08-24 13:09 639231735407682062
43 ms 52.144.29.9
30 2026-08-24 12:16 639231703815441688
2023 ms 52.144.29.9
29 2026-08-24 11:59 639231693747052549
20 ms 52.144.29.9
28 2026-08-24 11:43 639231683712487276
2029 ms 52.144.29.9
27 2026-08-24 11:26 639231673513573868
24 ms 52.144.29.9
26 2026-08-24 10:33 639231641791249939
36 ms 52.144.29.9
25 2026-08-24 10:16 639231631866211033
19 ms 52.144.29.9
24 2026-08-24 09:59 639231621644955316
15 ms 52.144.29.9
23 2026-08-24 09:42 639231611478799259
23 ms 52.144.29.9
22 2026-08-24 08:50 639231579923718211
30 ms 52.144.29.9
21 2026-08-24 08:33 639231569810702936
2046 ms 52.144.29.9
20 2026-08-24 08:16 639231559762411619
14 ms 52.144.29.9
19 2026-08-24 07:59 639231549663595407
25 ms 52.144.29.9
18 2026-08-24 07:07 639231518076817246
321 ms 52.144.29.9
17 2026-08-24 06:50 639231508078650885
5 ms 52.144.29.9
16 2026-08-24 06:33 639231498210697093
40 ms 52.144.29.9
15 2026-08-24 06:17 639231488109699360
20 ms 52.144.29.9
14 2026-08-24 05:24 639231456772510692
20 ms 52.144.29.9
13 2026-08-24 05:08 639231447084631185
36 ms 52.144.29.9
12 2026-08-24 04:52 639231437208519473
44 ms 52.144.29.9
11 2026-08-24 04:35 639231427209627490
12 ms 52.144.29.9
10 2026-08-24 03:43 639231395791246644
4 ms 52.144.29.9
9 2026-08-24 03:27 639231386075551458
2143 ms 52.144.29.9
8 2026-08-24 03:10 639231376208713791
17 ms 52.144.29.9
7 2026-08-24 02:53 639231366170589276
57 ms 52.144.29.9
6 2026-08-24 02:01 639231334732159368
15 ms 52.144.29.9
5 2026-08-24 01:45 639231325035670078
54 ms 52.144.29.9
4 2026-08-24 01:28 639231315132253837
19 ms 52.144.29.9
3 2026-08-24 01:11 639231305014280808
40 ms 52.144.29.9
2 2026-08-24 00:19 639231273779380675
19 ms 52.144.29.9
1 2026-08-24 00:03 639231264180839154
20 ms 52.144.29.9