Operations
Data status
Is the data current? Each connector is judged against its own schedule; the orbit block tells you how old the element sets behind live positions are.
Rendered 12 Sept 2026 03:03 UTC · Refresh← Platform statusSources & licenses
Orbital elements
Element set age
Latest epoch
just now
21 Sept 2026 14:50 UTC
Median element age
13.9 h
latest element set per object
Propagator objects
16,564
objects with usable elements
Connectors
Sync health
| Connector | Freshness | Last success | Last status | Next run | Duration | Failures | Circuit | Last failure |
|---|---|---|---|---|---|---|---|---|
| celestrak_gp CelesTrak · every 2 h | fresh | just now | success | in 2 h | 5.0 s | 0 | closed | none recorded |
| celestrak_satcat CelesTrak SATCAT · every 1 d | fresh | 8 h ago | failed | in 16 h | 5.3 s | 1 | closed | IntegrityError: (sqlalchemy.dialects.postgresql.asyncpg.IntegrityError) <class '… |
| celestrak_groups CelesTrak · every 2 h | fresh | 2 h ago | success | in 3 min | 61.3 s | 0 | closed | none recorded |
| derived_analytics SatelliteIndex (derived / curated) · every 1 h | fresh | 52 min ago | running | in 8 min | 2.1 min | 0 | closed | none recorded |
generated 12 Sept 2026 03:03 UTC · request 4de5a9a488ae42c5
Legend
Freshness thresholds
Connector freshness is relative to each connector’s own schedule: fresh when the last successful sync is younger than 3 × the interval, aging up to 12 × the interval, stale beyond that, unavailable when it never succeeded and not enabled for planned connectors.
- celestrak_gp: every 2 h → aging after 6 h, stale after 1 d
- celestrak_satcat: every 1 d → aging after 3 d, stale after 12 d
- celestrak_groups: every 2 h → aging after 6 h, stale after 1 d
- derived_analytics: every 1 h → aging after 3 h, stale after 12 h
Satellite pages use a second, per-object scale for the orbit itself: an element set is fresh under 12 h, aging between 12 and 48 h and stale beyond 48 h from its epoch (catalog metadata: 36 h / 96 h). Details in the methodology.