DNS response history for ns2.primvcm.com

ns2.primvcm.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-30. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 1034 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.primvcm.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

1034 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 08:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.200.235.254

Most recently resolved hosting IP on selected date

Successful Responses

28

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.primvcm.com

Showing DNS history for 2026-08-30 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
28 2026-08-30 08:48 639236755602384085
152 ms 31.200.235.254
27 2026-08-30 08:31 639236745600094925
2174 ms 31.200.235.254
26 2026-08-30 08:14 639236735311262753
2 ms 31.200.235.254
25 2026-08-30 07:57 639236724996745235
4 ms 31.200.235.254
24 2026-08-30 07:40 639236714839899761
3 ms 31.200.235.254
23 2026-08-30 07:23 639236704748431488
2007 ms 31.200.235.254
22 2026-08-30 07:06 639236694430128550
3 ms 31.200.235.254
21 2026-08-30 06:49 639236684143292417
4 ms 31.200.235.254
20 2026-08-30 06:32 639236673972499943
2168 ms 31.200.235.254
19 2026-08-30 05:38 639236642126522802
3 ms 31.200.235.254
18 2026-08-30 05:22 639236632183518198
2 ms 31.200.235.254
17 2026-08-30 05:05 639236622289312589
3 ms 31.200.235.254
16 2026-08-30 04:49 639236612490676525
2031 ms 31.200.235.254
15 2026-08-30 04:33 639236602582494852
3660 ms 31.200.235.254
14 2026-08-30 04:16 639236592511706469
3713 ms 31.200.235.254
13 2026-08-30 03:59 639236582441006869
3 ms 31.200.235.254
12 2026-08-30 03:43 639236572478785089
2152 ms 31.200.235.254
11 2026-08-30 03:26 639236562556749999
2164 ms 31.200.235.254
10 2026-08-30 03:09 639236552353482281
2168 ms 31.200.235.254
9 2026-08-30 02:52 639236542188881607
3 ms 31.200.235.254
8 2026-08-30 02:35 639236531885440105
156 ms 31.200.235.254
7 2026-08-30 01:41 639236499922985383
2 ms 31.200.235.254
6 2026-08-30 01:25 639236489713594431
2032 ms 31.200.235.254
5 2026-08-30 01:08 639236479750443901
3 ms 31.200.235.254
4 2026-08-30 00:51 639236469719936375
3 ms 31.200.235.254
3 2026-08-30 00:34 639236459579244885
3 ms 31.200.235.254
2 2026-08-30 00:18 639236449582837549
2165 ms 31.200.235.254
1 2026-08-30 00:01 639236439461653110
2165 ms 31.200.235.254