DNS response history for ns2.velarissoftware.com

ns2.velarissoftware.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 35 DNS check records, 34 successful responses, 1 failed responses, and 114 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.velarissoftware.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

114 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.5.5.165

Most recently resolved hosting IP on selected date

Successful Responses

34

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.velarissoftware.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
35 2026-08-26 11:51 639233414056832719
89 ms 5.5.5.165
34 2026-08-26 11:33 639233403515141099
95 ms 5.5.5.165
33 2026-08-26 10:39 639233370841350248
107 ms 5.5.5.165
32 2026-08-26 10:22 639233360361507238
189 ms 5.5.5.165
31 2026-08-26 10:04 639233350067824371
-
30 2026-08-26 09:47 639233339545274518
155 ms 5.5.5.165
29 2026-08-26 09:30 639233329214918079
86 ms 5.5.5.165
28 2026-08-26 09:12 639233318749762337
93 ms 5.5.5.165
27 2026-08-26 08:55 639233308387917838
113 ms 5.5.5.165
26 2026-08-26 08:38 639233297961740122
118 ms 5.5.5.165
25 2026-08-26 08:20 639233287487159094
43 ms 5.5.5.165
24 2026-08-26 08:03 639233276995531707
93 ms 5.5.5.165
23 2026-08-26 07:45 639233266521568229
98 ms 5.5.5.165
22 2026-08-26 07:28 639233256081047431
99 ms 5.5.5.165
21 2026-08-26 06:34 639233223620132921
96 ms 5.5.5.165
20 2026-08-26 06:17 639233213287814244
138 ms 5.5.5.165
19 2026-08-26 05:59 639233202925983161
87 ms 5.5.5.165
18 2026-08-26 05:42 639233192644780696
82 ms 5.5.5.165
17 2026-08-26 05:25 639233182401183833
150 ms 5.5.5.165
16 2026-08-26 05:08 639233172074181051
83 ms 5.5.5.165
15 2026-08-26 04:51 639233161808421455
86 ms 5.5.5.165
14 2026-08-26 04:33 639233151357344052
160 ms 5.5.5.165
13 2026-08-26 04:16 639233141034116946
83 ms 5.5.5.165
12 2026-08-26 03:59 639233130828334142
107 ms 5.5.5.165
11 2026-08-26 03:42 639233120373450007
96 ms 5.5.5.165
10 2026-08-26 03:24 639233110066216193
92 ms 5.5.5.165
9 2026-08-26 02:31 639233078065410564
93 ms 5.5.5.165
8 2026-08-26 02:14 639233067787457832
88 ms 5.5.5.165
7 2026-08-26 01:57 639233057501801162
82 ms 5.5.5.165
6 2026-08-26 01:39 639233047089431703
328 ms 5.5.5.165
5 2026-08-26 01:22 639233036754790688
148 ms 5.5.5.165
4 2026-08-26 01:05 639233026412602472
126 ms 5.5.5.165
3 2026-08-26 00:48 639233016064066127
143 ms 5.5.5.165
2 2026-08-26 00:31 639233005922655772
107 ms 5.5.5.165
1 2026-08-26 00:14 639232995672256907
133 ms 5.5.5.165