DNS response history for ns2.vps40323.nodevm.com

ns2.vps40323.nodevm.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-24. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 266 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.vps40323.nodevm.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

266 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.71.168

Most recently resolved hosting IP on selected date

Successful Responses

33

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.vps40323.nodevm.com

Showing DNS history for 2026-08-24 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
33 2026-08-24 13:50 639231755868832964
121 ms 165.140.71.168
32 2026-08-24 13:33 639231745628278877
123 ms 165.140.71.168
31 2026-08-24 13:16 639231735407682062
239 ms 165.140.71.168
30 2026-08-24 12:23 639231703815441688
243 ms 165.140.71.168
29 2026-08-24 12:07 639231693747052549
249 ms 165.140.71.168
28 2026-08-24 11:50 639231683712487276
242 ms 165.140.71.168
27 2026-08-24 11:33 639231673513573868
239 ms 165.140.71.168
26 2026-08-24 10:40 639231641791249939
121 ms 165.140.71.168
25 2026-08-24 10:23 639231631866211033
239 ms 165.140.71.168
24 2026-08-24 10:07 639231621644955316
122 ms 165.140.71.168
23 2026-08-24 09:49 639231611478799259
126 ms 165.140.71.168
22 2026-08-24 08:57 639231579923718211
123 ms 165.140.71.168
21 2026-08-24 08:40 639231569810702936
238 ms 165.140.71.168
20 2026-08-24 08:23 639231559762411619
238 ms 165.140.71.168
19 2026-08-24 08:06 639231549663595407
124 ms 165.140.71.168
18 2026-08-24 07:14 639231518076817246
231 ms 165.140.71.168
17 2026-08-24 06:57 639231508078650885
239 ms 165.140.71.168
16 2026-08-24 06:41 639231498210697093
2245 ms 165.140.71.168
15 2026-08-24 06:24 639231488109699360
312 ms 165.140.71.168
14 2026-08-24 05:32 639231456772510692
122 ms 165.140.71.168
13 2026-08-24 05:15 639231447084631185
133 ms 165.140.71.168
12 2026-08-24 04:59 639231437208519473
238 ms 165.140.71.168
11 2026-08-24 04:42 639231427209627490
243 ms 165.140.71.168
10 2026-08-24 03:50 639231395791246644
239 ms 165.140.71.168
9 2026-08-24 03:34 639231386075551458
120 ms 165.140.71.168
8 2026-08-24 03:17 639231376208713791
313 ms 165.140.71.168
7 2026-08-24 03:01 639231366170589276
329 ms 165.140.71.168
6 2026-08-24 02:08 639231334732159368
242 ms 165.140.71.168
5 2026-08-24 01:52 639231325035670078
122 ms 165.140.71.168
4 2026-08-24 01:35 639231315132253837
239 ms 165.140.71.168
3 2026-08-24 01:19 639231305014280808
239 ms 165.140.71.168
2 2026-08-24 00:26 639231273779380675
119 ms 165.140.71.168
1 2026-08-24 00:11 639231264180839154
253 ms 165.140.71.168