DNS response history for ns2.vanoppen.com

ns2.vanoppen.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 486 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.vanoppen.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

486 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.104.14.170

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 ns2.vanoppen.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:50 639233414056832719
2195 ms 172.104.14.170
34 2026-08-26 11:33 639233403515141099
210 ms 172.104.14.170
33 2026-08-26 10:38 639233370841350248
216 ms 172.104.14.170
32 2026-08-26 10:21 639233360361507238
2215 ms 172.104.14.170
31 2026-08-26 10:04 639233350067824371
9 ms 172.104.14.170
30 2026-08-26 09:46 639233339545274518
199 ms 172.104.14.170
29 2026-08-26 09:29 639233329214918079
224 ms 172.104.14.170
28 2026-08-26 09:12 639233318749762337
172 ms 172.104.14.170
27 2026-08-26 08:54 639233308387917838
218 ms 172.104.14.170
26 2026-08-26 08:37 639233297961740122
205 ms 172.104.14.170
25 2026-08-26 08:20 639233287487159094
218 ms 172.104.14.170
24 2026-08-26 08:02 639233276995531707
92 ms 172.104.14.170
23 2026-08-26 07:44 639233266521568229
213 ms 172.104.14.170
22 2026-08-26 07:27 639233256081047431
8 ms 172.104.14.170
21 2026-08-26 06:33 639233223620132921
105 ms 172.104.14.170
20 2026-08-26 06:16 639233213287814244
7 ms 172.104.14.170
19 2026-08-26 05:58 639233202925983161
2033 ms 172.104.14.170
18 2026-08-26 05:41 639233192644780696
150 ms 172.104.14.170
17 2026-08-26 05:24 639233182401183833
9 ms 172.104.14.170
16 2026-08-26 05:07 639233172074181051
112 ms 172.104.14.170
15 2026-08-26 04:50 639233161808421455
8 ms 172.104.14.170
14 2026-08-26 04:33 639233151357344052
196 ms 172.104.14.170
13 2026-08-26 04:15 639233141034116946
208 ms 172.104.14.170
12 2026-08-26 03:58 639233130828334142
2107 ms 172.104.14.170
11 2026-08-26 03:41 639233120373450007
214 ms 172.104.14.170
10 2026-08-26 03:24 639233110066216193
100 ms 172.104.14.170
9 2026-08-26 02:30 639233078065410564
14 ms 172.104.14.170
8 2026-08-26 02:13 639233067787457832
176 ms 172.104.14.170
7 2026-08-26 01:56 639233057501801162
2100 ms 172.104.14.170
6 2026-08-26 01:39 639233047089431703
98 ms 172.104.14.170
5 2026-08-26 01:22 639233036754790688
359 ms 172.104.14.170
4 2026-08-26 01:04 639233026412602472
109 ms 172.104.14.170
3 2026-08-26 00:47 639233016064066127
105 ms 172.104.14.170
2 2026-08-26 00:30 639233005922655772
2187 ms 172.104.14.170
1 2026-08-26 00:13 639232995672256907
230 ms 172.104.14.170