DNS response history for ns2.versens.net

ns2.versens.net 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 30 DNS check records, 30 successful responses, 0 failed responses, and 118 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.versens.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

118 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.18.168.135

Most recently resolved hosting IP on selected date

Successful Responses

30

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.versens.net

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
30 2026-08-24 12:21 639231703815441688
92 ms 217.18.168.135
29 2026-08-24 12:04 639231693747052549
106 ms 217.18.168.135
28 2026-08-24 11:48 639231683712487276
82 ms 217.18.168.135
27 2026-08-24 11:31 639231673513573868
255 ms 217.18.168.135
26 2026-08-24 10:38 639231641791249939
36 ms 217.18.168.135
25 2026-08-24 10:21 639231631866211033
162 ms 217.18.168.135
24 2026-08-24 10:04 639231621644955316
62 ms 217.18.168.135
23 2026-08-24 09:47 639231611478799259
161 ms 217.18.168.135
22 2026-08-24 08:55 639231579923718211
93 ms 217.18.168.135
21 2026-08-24 08:38 639231569810702936
164 ms 217.18.168.135
20 2026-08-24 08:21 639231559762411619
13 ms 217.18.168.135
19 2026-08-24 08:04 639231549663595407
167 ms 217.18.168.135
18 2026-08-24 07:12 639231518076817246
159 ms 217.18.168.135
17 2026-08-24 06:55 639231508078650885
84 ms 217.18.168.135
16 2026-08-24 06:39 639231498210697093
46 ms 217.18.168.135
15 2026-08-24 06:22 639231488109699360
183 ms 217.18.168.135
14 2026-08-24 05:30 639231456772510692
257 ms 217.18.168.135
13 2026-08-24 05:13 639231447084631185
46 ms 217.18.168.135
12 2026-08-24 04:57 639231437208519473
173 ms 217.18.168.135
11 2026-08-24 04:40 639231427209627490
159 ms 217.18.168.135
10 2026-08-24 03:48 639231395791246644
164 ms 217.18.168.135
9 2026-08-24 03:32 639231386075551458
53 ms 217.18.168.135
8 2026-08-24 03:15 639231376208713791
46 ms 217.18.168.135
7 2026-08-24 02:59 639231366170589276
85 ms 217.18.168.135
6 2026-08-24 02:06 639231334732159368
168 ms 217.18.168.135
5 2026-08-24 01:50 639231325035670078
62 ms 217.18.168.135
4 2026-08-24 01:33 639231315132253837
95 ms 217.18.168.135
3 2026-08-24 01:17 639231305014280808
39 ms 217.18.168.135
2 2026-08-24 00:24 639231273779380675
162 ms 217.18.168.135
1 2026-08-24 00:09 639231264180839154
160 ms 217.18.168.135