- This topic has 7 replies, 2 voices, and was last updated 1 week, 3 days ago by
.
-
Posts
-
Hi,
Two things may be contributing to this.
First, CelesTrak (the source for the AMSAT TLE data) enforces rate limiting and can temporarily block an IP address that makes too many requests. Helioclock fetches the AMSAT TLE set once daily at 10:00 UTC. If CelesTrak has blocked your unit’s IP, the fetch will fail silently and show as DELAYED. This is usually temporary — the block clears on its own. If you’re on a shared IP (business network, ISP NAT), other users on that same IP hitting CelesTrak can trigger the block even if Helioclock itself is being well-behaved.
Second, worth knowing: CelesTrak ran out of 5-digit satellite catalog numbers in July 2026. Newly cataloged satellites since then have 6-digit numbers and are not available in the legacy TLE format that Helioclock currently uses. This means any satellites launched after mid-July 2026 will not appear in the AMSAT set — but established satellites like SO-50, AO-91, and most of the active AMSAT fleet are unaffected since they were cataloged well before that cutoff.
A software update to address this 5-to-6 digit migration is planned for a future release. When that ships, Helioclock will switch to CelesTrak’s newer data format that fully supports the expanded catalog numbers.
If you can tell me which specific satellites are showing as missing or DELAYED, that will help determine which issue you’re hitting.
Anthony
KA9NWMI appear to be blocked. I tried a VPN service and I could get to the website whereby without I cannot.
terrific.
- You must be logged in to reply to this topic.