DNS response history for ns1.chaselight.net

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

35

Historical checks stored for this nameserver on selected date

Average Latency

345 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.16.232.33

Most recently resolved hosting IP on selected date

Successful Responses

35

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.chaselight.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
35 2026-08-26 11:52 639233414056832719
151 ms 69.16.232.33
34 2026-08-26 11:34 639233403515141099
329 ms 69.16.232.33
33 2026-08-26 10:39 639233370841350248
241 ms 69.16.232.33
32 2026-08-26 10:22 639233360361507238
7 ms 69.16.232.33
31 2026-08-26 10:05 639233350067824371
219 ms 69.16.232.33
30 2026-08-26 09:48 639233339545274518
7 ms 69.16.232.33
29 2026-08-26 09:30 639233329214918079
220 ms 69.16.232.33
28 2026-08-26 09:13 639233318749762337
169 ms 69.16.232.33
27 2026-08-26 08:56 639233308387917838
229 ms 69.16.232.33
26 2026-08-26 08:38 639233297961740122
234 ms 69.16.232.33
25 2026-08-26 08:21 639233287487159094
241 ms 69.16.232.33
24 2026-08-26 08:03 639233276995531707
233 ms 69.16.232.33
23 2026-08-26 07:46 639233266521568229
238 ms 69.16.232.33
22 2026-08-26 07:28 639233256081047431
231 ms 69.16.232.33
21 2026-08-26 06:34 639233223620132921
2146 ms 69.16.232.33
20 2026-08-26 06:17 639233213287814244
11 ms 69.16.232.33
19 2026-08-26 06:00 639233202925983161
113 ms 69.16.232.33
18 2026-08-26 05:43 639233192644780696
2114 ms 69.16.232.33
17 2026-08-26 05:25 639233182401183833
16 ms 69.16.232.33
16 2026-08-26 05:08 639233172074181051
235 ms 69.16.232.33
15 2026-08-26 04:51 639233161808421455
227 ms 69.16.232.33
14 2026-08-26 04:34 639233151357344052
228 ms 69.16.232.33
13 2026-08-26 04:17 639233141034116946
119 ms 69.16.232.33
12 2026-08-26 04:00 639233130828334142
234 ms 69.16.232.33
11 2026-08-26 03:42 639233120373450007
237 ms 69.16.232.33
10 2026-08-26 03:25 639233110066216193
123 ms 69.16.232.33
9 2026-08-26 02:32 639233078065410564
222 ms 69.16.232.33
8 2026-08-26 02:14 639233067787457832
141 ms 69.16.232.33
7 2026-08-26 01:57 639233057501801162
232 ms 69.16.232.33
6 2026-08-26 01:40 639233047089431703
215 ms 69.16.232.33
5 2026-08-26 01:23 639233036754790688
225 ms 69.16.232.33
4 2026-08-26 01:06 639233026412602472
216 ms 69.16.232.33
3 2026-08-26 00:48 639233016064066127
128 ms 69.16.232.33
2 2026-08-26 00:31 639233005922655772
2008 ms 69.16.232.33
1 2026-08-26 00:14 639232995672256907
124 ms 69.16.232.33