DNS response history for ns2.vweb.digital

ns2.vweb.digital 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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 304 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.vweb.digital.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.109.20.170

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.vweb.digital

Showing DNS history for 2026-08-25 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-25 10:13 639232492740373468
68 ms 65.109.20.170
29 2026-08-25 09:56 639232482235303141
133 ms 65.109.20.170
28 2026-08-25 09:39 639232471861770303
123 ms 65.109.20.170
27 2026-08-25 09:22 639232461630217327
189 ms 65.109.20.170
26 2026-08-25 09:04 639232451282965990
10 ms 65.109.20.170
25 2026-08-25 08:47 639232440814614938
2059 ms 65.109.20.170
24 2026-08-25 08:30 639232430410720425
150 ms 65.109.20.170
23 2026-08-25 08:12 639232420003096185
73 ms 65.109.20.170
22 2026-08-25 07:55 639232409467287444
12 ms 65.109.20.170
21 2026-08-25 07:38 639232399077195997
320 ms 65.109.20.170
20 2026-08-25 07:20 639232388731528337
49 ms 65.109.20.170
19 2026-08-25 07:03 639232378288598612
262 ms 65.109.20.170
18 2026-08-25 06:09 639232346196373643
139 ms 65.109.20.170
17 2026-08-25 05:52 639232336112370741
54 ms 65.109.20.170
16 2026-08-25 05:36 639232326146508970
121 ms 65.109.20.170
15 2026-08-25 05:19 639232316189381720
56 ms 65.109.20.170
14 2026-08-25 05:03 639232306217998913
58 ms 65.109.20.170
13 2026-08-25 04:46 639232296255744174
60 ms 65.109.20.170
12 2026-08-25 04:29 639232286095760789
133 ms 65.109.20.170
11 2026-08-25 04:12 639232276086186273
52 ms 65.109.20.170
10 2026-08-25 03:56 639232265900986425
2213 ms 65.109.20.170
9 2026-08-25 03:39 639232255723518075
290 ms 65.109.20.170
8 2026-08-25 03:22 639232245484452890
131 ms 65.109.20.170
7 2026-08-25 03:04 639232235157175331
145 ms 65.109.20.170
6 2026-08-25 02:11 639232203197189095
127 ms 65.109.20.170
5 2026-08-25 01:54 639232192844564298
49 ms 65.109.20.170
4 2026-08-25 01:37 639232182496008942
739 ms 65.109.20.170
3 2026-08-25 01:19 639232172197053132
41 ms 65.109.20.170
2 2026-08-25 00:26 639232140250307418
119 ms 65.109.20.170
1 2026-08-25 00:09 639232129927860324
1135 ms 65.109.20.170