Real-time service health, queried from the production API by your browser — plus an honest account of how this platform is operated and what we do and do not guarantee.
The values below are fetched from the production API by your browser, right now — this is not a cached badge or a hand-edited status. If the API were down, these fields would fail to load.
| Public API | Checking… |
|---|---|
| Aircraft currently tracked | … |
| Last upstream fetch | … |
| Active grid cells | … |
| API process uptime | … |
| ML service | Checking… |
| ML engines | … |
| Component | Function | Failure behaviour |
|---|---|---|
| Ingest & fusion | Polls upstream ADS-B feeds, de-duplicates by ICAO 24-bit address | Individual feed failure degrades coverage but does not stop the platform; remaining feeds continue. |
| Enrichment pipeline | Type/operator lookup, attention scoring, integrity checks | A watchdog aborts a hung cycle so the pipeline cannot wedge indefinitely. |
| Anomaly / ML service | Consensus anomaly detection, trajectory and baseline analysis | Isolated from the API. If it restarts, the API serves the last known-good analysis rather than failing. |
| Web & API | Live map, REST, WebSocket, MCP endpoint | Stateless; served behind a CDN with automatic process restart. |
AeroScope is maintained by a named individual researcher, not a staffed operations team. That shapes what we can and cannot promise, and we would rather state it plainly than imply otherwise: