DNS response history for ns1.cavsme.net

ns1.cavsme.net 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 36 DNS check records, 36 successful responses, 0 failed responses, and 472 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 ns1.cavsme.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

472 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.163.180

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns1.cavsme.net

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
36 2026-08-26 11:54 639233414056832719
358 ms 162.240.163.180
35 2026-08-26 11:37 639233403515141099
354 ms 162.240.163.180
34 2026-08-26 10:42 639233370841350248
357 ms 162.240.163.180
33 2026-08-26 10:25 639233360361507238
182 ms 162.240.163.180
32 2026-08-26 10:07 639233350067824371
2187 ms 162.240.163.180
31 2026-08-26 09:50 639233339545274518
358 ms 162.240.163.180
30 2026-08-26 09:33 639233329214918079
355 ms 162.240.163.180
29 2026-08-26 09:15 639233318749762337
382 ms 162.240.163.180
28 2026-08-26 08:58 639233308387917838
382 ms 162.240.163.180
27 2026-08-26 08:41 639233297961740122
378 ms 162.240.163.180
26 2026-08-26 08:23 639233287487159094
384 ms 162.240.163.180
25 2026-08-26 08:06 639233276995531707
377 ms 162.240.163.180
24 2026-08-26 07:48 639233266521568229
201 ms 162.240.163.180
23 2026-08-26 07:31 639233256081047431
347 ms 162.240.163.180
22 2026-08-26 06:37 639233223620132921
347 ms 162.240.163.180
21 2026-08-26 06:20 639233213287814244
203 ms 162.240.163.180
20 2026-08-26 06:02 639233202925983161
350 ms 162.240.163.180
19 2026-08-26 05:45 639233192644780696
353 ms 162.240.163.180
18 2026-08-26 05:28 639233182401183833
351 ms 162.240.163.180
17 2026-08-26 05:11 639233172074181051
244 ms 162.240.163.180
16 2026-08-26 04:54 639233161808421455
354 ms 162.240.163.180
15 2026-08-26 04:37 639233151357344052
3 ms 162.240.163.180
14 2026-08-26 04:19 639233141034116946
185 ms 162.240.163.180
13 2026-08-26 04:02 639233130828334142
2009 ms 162.240.163.180
12 2026-08-26 03:45 639233120373450007
350 ms 162.240.163.180
11 2026-08-26 03:27 639233110066216193
348 ms 162.240.163.180
10 2026-08-26 02:34 639233078065410564
348 ms 162.240.163.180
9 2026-08-26 02:17 639233067787457832
351 ms 162.240.163.180
8 2026-08-26 02:00 639233057501801162
349 ms 162.240.163.180
7 2026-08-26 01:43 639233047089431703
347 ms 162.240.163.180
6 2026-08-26 01:25 639233036754790688
360 ms 162.240.163.180
5 2026-08-26 01:08 639233026412602472
353 ms 162.240.163.180
4 2026-08-26 00:51 639233016064066127
207 ms 162.240.163.180
3 2026-08-26 00:34 639233005922655772
347 ms 162.240.163.180
2 2026-08-26 00:17 639232995672256907
2279 ms 162.240.163.180
1 2026-08-26 00:00 639232985300872416
349 ms 162.240.163.180