DNS response history for ns2.vapssky.com

ns2.vapssky.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 332 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.vapssky.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

332 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

151.106.112.212

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.vapssky.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:53 639233414056832719
340 ms 151.106.112.212
34 2026-08-26 11:36 639233403515141099
350 ms 151.106.112.212
33 2026-08-26 10:41 639233370841350248
339 ms 151.106.112.212
32 2026-08-26 10:24 639233360361507238
335 ms 151.106.112.212
31 2026-08-26 10:06 639233350067824371
338 ms 151.106.112.212
30 2026-08-26 09:49 639233339545274518
336 ms 151.106.112.212
29 2026-08-26 09:32 639233329214918079
394 ms 151.106.112.212
28 2026-08-26 09:14 639233318749762337
343 ms 151.106.112.212
27 2026-08-26 08:57 639233308387917838
342 ms 151.106.112.212
26 2026-08-26 08:40 639233297961740122
341 ms 151.106.112.212
25 2026-08-26 08:22 639233287487159094
192 ms 151.106.112.212
24 2026-08-26 08:05 639233276995531707
342 ms 151.106.112.212
23 2026-08-26 07:47 639233266521568229
337 ms 151.106.112.212
22 2026-08-26 07:30 639233256081047431
334 ms 151.106.112.212
21 2026-08-26 06:36 639233223620132921
343 ms 151.106.112.212
20 2026-08-26 06:19 639233213287814244
342 ms 151.106.112.212
19 2026-08-26 06:01 639233202925983161
345 ms 151.106.112.212
18 2026-08-26 05:44 639233192644780696
337 ms 151.106.112.212
17 2026-08-26 05:27 639233182401183833
332 ms 151.106.112.212
16 2026-08-26 05:10 639233172074181051
346 ms 151.106.112.212
15 2026-08-26 04:53 639233161808421455
348 ms 151.106.112.212
14 2026-08-26 04:36 639233151357344052
347 ms 151.106.112.212
13 2026-08-26 04:18 639233141034116946
331 ms 151.106.112.212
12 2026-08-26 04:01 639233130828334142
342 ms 151.106.112.212
11 2026-08-26 03:44 639233120373450007
329 ms 151.106.112.212
10 2026-08-26 03:26 639233110066216193
340 ms 151.106.112.212
9 2026-08-26 02:33 639233078065410564
332 ms 151.106.112.212
8 2026-08-26 02:16 639233067787457832
335 ms 151.106.112.212
7 2026-08-26 01:59 639233057501801162
339 ms 151.106.112.212
6 2026-08-26 01:42 639233047089431703
329 ms 151.106.112.212
5 2026-08-26 01:24 639233036754790688
191 ms 151.106.112.212
4 2026-08-26 01:07 639233026412602472
336 ms 151.106.112.212
3 2026-08-26 00:50 639233016064066127
337 ms 151.106.112.212
2 2026-08-26 00:33 639233005922655772
332 ms 151.106.112.212
1 2026-08-26 00:16 639232995672256907
338 ms 151.106.112.212