DNS response history for ns1.chavalusa.com

ns1.chavalusa.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 245 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.chavalusa.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

245 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

174.136.29.99

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 ns1.chavalusa.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:46 639233445367152284
269 ms 174.136.29.99
37 2026-08-26 12:29 639233434974187439
7 ms 174.136.29.99
36 2026-08-26 12:11 639233424567558554
284 ms 174.136.29.99
35 2026-08-26 11:54 639233414056832719
121 ms 174.136.29.99
34 2026-08-26 11:36 639233403515141099
275 ms 174.136.29.99
33 2026-08-26 10:42 639233370841350248
279 ms 174.136.29.99
32 2026-08-26 10:24 639233360361507238
276 ms 174.136.29.99
31 2026-08-26 10:07 639233350067824371
272 ms 174.136.29.99
30 2026-08-26 09:50 639233339545274518
164 ms 174.136.29.99
29 2026-08-26 09:32 639233329214918079
280 ms 174.136.29.99
28 2026-08-26 09:15 639233318749762337
269 ms 174.136.29.99
27 2026-08-26 08:58 639233308387917838
295 ms 174.136.29.99
26 2026-08-26 08:40 639233297961740122
273 ms 174.136.29.99
25 2026-08-26 08:23 639233287487159094
272 ms 174.136.29.99
24 2026-08-26 08:06 639233276995531707
275 ms 174.136.29.99
23 2026-08-26 07:48 639233266521568229
273 ms 174.136.29.99
22 2026-08-26 07:30 639233256081047431
266 ms 174.136.29.99
21 2026-08-26 06:37 639233223620132921
271 ms 174.136.29.99
20 2026-08-26 06:19 639233213287814244
265 ms 174.136.29.99
19 2026-08-26 06:02 639233202925983161
267 ms 174.136.29.99
18 2026-08-26 05:45 639233192644780696
274 ms 174.136.29.99
17 2026-08-26 05:28 639233182401183833
275 ms 174.136.29.99
16 2026-08-26 05:11 639233172074181051
281 ms 174.136.29.99
15 2026-08-26 04:53 639233161808421455
266 ms 174.136.29.99
14 2026-08-26 04:36 639233151357344052
193 ms 174.136.29.99
13 2026-08-26 04:19 639233141034116946
272 ms 174.136.29.99
12 2026-08-26 04:02 639233130828334142
277 ms 174.136.29.99
11 2026-08-26 03:44 639233120373450007
273 ms 174.136.29.99
10 2026-08-26 03:27 639233110066216193
271 ms 174.136.29.99
9 2026-08-26 02:34 639233078065410564
274 ms 174.136.29.99
8 2026-08-26 02:17 639233067787457832
150 ms 174.136.29.99
7 2026-08-26 02:00 639233057501801162
319 ms 174.136.29.99
6 2026-08-26 01:42 639233047089431703
272 ms 174.136.29.99
5 2026-08-26 01:25 639233036754790688
273 ms 174.136.29.99
4 2026-08-26 01:08 639233026412602472
11 ms 174.136.29.99
3 2026-08-26 00:51 639233016064066127
285 ms 174.136.29.99
2 2026-08-26 00:33 639233005922655772
268 ms 174.136.29.99
1 2026-08-26 00:16 639232995672256907
124 ms 174.136.29.99