DNS response history for ns1.heycast.app

ns1.heycast.app 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 30 DNS check records, 30 successful responses, 0 failed responses, and 372 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.heycast.app.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

372 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

194.29.100.103

Most recently resolved hosting IP on selected date

Successful Responses

30

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.heycast.app

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
30 2026-08-26 09:33 639233329214918079
6 ms 194.29.100.103
29 2026-08-26 09:16 639233318749762337
6 ms 194.29.100.103
28 2026-08-26 08:58 639233308387917838
329 ms 194.29.100.103
27 2026-08-26 08:41 639233297961740122
307 ms 194.29.100.103
26 2026-08-26 08:23 639233287487159094
319 ms 194.29.100.103
25 2026-08-26 08:06 639233276995531707
427 ms 194.29.100.103
24 2026-08-26 07:48 639233266521568229
332 ms 194.29.100.103
23 2026-08-26 07:31 639233256081047431
320 ms 194.29.100.103
22 2026-08-26 06:37 639233223620132921
1254 ms 194.29.100.103
21 2026-08-26 06:20 639233213287814244
311 ms 194.29.100.103
20 2026-08-26 06:02 639233202925983161
307 ms 194.29.100.103
19 2026-08-26 05:45 639233192644780696
305 ms 194.29.100.103
18 2026-08-26 05:28 639233182401183833
285 ms 194.29.100.103
17 2026-08-26 05:11 639233172074181051
302 ms 194.29.100.103
16 2026-08-26 04:54 639233161808421455
308 ms 194.29.100.103
15 2026-08-26 04:37 639233151357344052
302 ms 194.29.100.103
14 2026-08-26 04:19 639233141034116946
287 ms 194.29.100.103
13 2026-08-26 04:02 639233130828334142
181 ms 194.29.100.103
12 2026-08-26 03:45 639233120373450007
304 ms 194.29.100.103
11 2026-08-26 03:28 639233110066216193
2252 ms 194.29.100.103
10 2026-08-26 02:34 639233078065410564
308 ms 194.29.100.103
9 2026-08-26 02:17 639233067787457832
312 ms 194.29.100.103
8 2026-08-26 02:00 639233057501801162
7 ms 194.29.100.103
7 2026-08-26 01:43 639233047089431703
268 ms 194.29.100.103
6 2026-08-26 01:26 639233036754790688
311 ms 194.29.100.103
5 2026-08-26 01:08 639233026412602472
307 ms 194.29.100.103
4 2026-08-26 00:51 639233016064066127
319 ms 194.29.100.103
3 2026-08-26 00:34 639233005922655772
280 ms 194.29.100.103
2 2026-08-26 00:17 639232995672256907
311 ms 194.29.100.103
1 2026-08-26 00:00 639232985300872416
306 ms 194.29.100.103