DNS response history for ns2.server-nvme.com

ns2.server-nvme.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 38 DNS check records, 38 successful responses, 0 failed responses, and 319 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.server-nvme.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

319 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.88.64.12

Most recently resolved hosting IP on selected date

Successful Responses

38

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.server-nvme.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
38 2026-08-26 12:39 639233445367152284
63 ms 23.88.64.12
37 2026-08-26 12:22 639233434974187439
2027 ms 23.88.64.12
36 2026-08-26 12:04 639233424567558554
78 ms 23.88.64.12
35 2026-08-26 11:47 639233414056832719
37 ms 23.88.64.12
34 2026-08-26 11:29 639233403515141099
59 ms 23.88.64.12
33 2026-08-26 10:35 639233370841350248
58 ms 23.88.64.12
32 2026-08-26 10:17 639233360361507238
78 ms 23.88.64.12
31 2026-08-26 10:00 639233350067824371
80 ms 23.88.64.12
30 2026-08-26 09:43 639233339545274518
57 ms 23.88.64.12
29 2026-08-26 09:25 639233329214918079
58 ms 23.88.64.12
28 2026-08-26 09:08 639233318749762337
10 ms 23.88.64.12
27 2026-08-26 08:51 639233308387917838
81 ms 23.88.64.12
26 2026-08-26 08:33 639233297961740122
2017 ms 23.88.64.12
25 2026-08-26 08:16 639233287487159094
74 ms 23.88.64.12
24 2026-08-26 07:58 639233276995531707
57 ms 23.88.64.12
23 2026-08-26 07:41 639233266521568229
52 ms 23.88.64.12
22 2026-08-26 07:24 639233256081047431
48 ms 23.88.64.12
21 2026-08-26 06:30 639233223620132921
47 ms 23.88.64.12
20 2026-08-26 06:12 639233213287814244
2027 ms 23.88.64.12
19 2026-08-26 05:55 639233202925983161
2019 ms 23.88.64.12
18 2026-08-26 05:38 639233192644780696
66 ms 23.88.64.12
17 2026-08-26 05:21 639233182401183833
80 ms 23.88.64.12
16 2026-08-26 05:04 639233172074181051
2050 ms 23.88.64.12
15 2026-08-26 04:46 639233161808421455
56 ms 23.88.64.12
14 2026-08-26 04:29 639233151357344052
57 ms 23.88.64.12
13 2026-08-26 04:12 639233141034116946
43 ms 23.88.64.12
12 2026-08-26 03:55 639233130828334142
67 ms 23.88.64.12
11 2026-08-26 03:37 639233120373450007
44 ms 23.88.64.12
10 2026-08-26 03:20 639233110066216193
65 ms 23.88.64.12
9 2026-08-26 02:27 639233078065410564
86 ms 23.88.64.12
8 2026-08-26 02:10 639233067787457832
72 ms 23.88.64.12
7 2026-08-26 01:53 639233057501801162
47 ms 23.88.64.12
6 2026-08-26 01:35 639233047089431703
63 ms 23.88.64.12
5 2026-08-26 01:18 639233036754790688
38 ms 23.88.64.12
4 2026-08-26 01:01 639233026412602472
82 ms 23.88.64.12
3 2026-08-26 00:44 639233016064066127
35 ms 23.88.64.12
2 2026-08-26 00:27 639233005922655772
83 ms 23.88.64.12
1 2026-08-26 00:10 639232995672256907
69 ms 23.88.64.12