DNS response history for ns2.dpvps.com

ns2.dpvps.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-29. For this date, NameServerHistory found 36 DNS check records, 35 successful responses, 1 failed responses, and 246 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.dpvps.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.201.50.220

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.dpvps.com

Showing DNS history for 2026-08-29 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
36 2026-08-29 12:21 639236028175589918
20 ms 185.201.50.220
35 2026-08-29 12:04 639236017965421028
4 ms 185.201.50.220
34 2026-08-29 11:47 639236007792625266
7 ms 185.201.50.220
33 2026-08-29 11:30 639235997602806960
3 ms 185.201.50.220
32 2026-08-29 11:14 639235987487833458
51 ms 185.201.50.220
31 2026-08-29 10:57 639235977211002296
14 ms 185.201.50.220
30 2026-08-29 10:39 639235966864596836
9 ms 185.201.50.220
29 2026-08-29 10:22 639235956590882003
8 ms 185.201.50.220
28 2026-08-29 09:29 639235924465736791
2055 ms 185.201.50.220
27 2026-08-29 09:12 639235914430611197
3 ms 185.201.50.220
26 2026-08-29 08:55 639235904343784853
8 ms 185.201.50.220
25 2026-08-29 08:38 639235894201078068
8 ms 185.201.50.220
24 2026-08-29 08:21 639235884233447452
5 ms 185.201.50.220
23 2026-08-29 08:05 639235874142207309
40 ms 185.201.50.220
22 2026-08-29 07:48 639235863974652466
19 ms 185.201.50.220
21 2026-08-29 07:31 639235853716243436
-
20 2026-08-29 07:14 639235843614494759
6 ms 185.201.50.220
19 2026-08-29 06:57 639235833401459551
30 ms 185.201.50.220
18 2026-08-29 06:40 639235823220464528
25 ms 185.201.50.220
17 2026-08-29 06:23 639235812997510905
24 ms 185.201.50.220
16 2026-08-29 05:30 639235781101962521
18 ms 185.201.50.220
15 2026-08-29 05:13 639235771207673260
5 ms 185.201.50.220
14 2026-08-29 04:56 639235761047429642
3 ms 185.201.50.220
13 2026-08-29 04:39 639235750964347246
2008 ms 185.201.50.220
12 2026-08-29 04:23 639235740923490874
15 ms 185.201.50.220
11 2026-08-29 04:06 639235730842894399
8 ms 185.201.50.220
10 2026-08-29 03:49 639235720760084717
4 ms 185.201.50.220
9 2026-08-29 03:32 639235710843666743
30 ms 185.201.50.220
8 2026-08-29 03:16 639235700733510561
8 ms 185.201.50.220
7 2026-08-29 02:59 639235690509906192
23 ms 185.201.50.220
6 2026-08-29 02:41 639235680156673501
2032 ms 185.201.50.220
5 2026-08-29 02:24 639235669720606443
4 ms 185.201.50.220
4 2026-08-29 01:30 639235637451417084
14 ms 185.201.50.220
3 2026-08-29 01:13 639235627307383453
2023 ms 185.201.50.220
2 2026-08-29 00:56 639235616906386856
32 ms 185.201.50.220
1 2026-08-29 00:39 639235606582912691
28 ms 185.201.50.220