SYSTEM STATUS
ClearProp status
Checking status…
Last checked --:-- UTC · live status refreshes about once a minute · history recorded every 15 minutes
ROUTE + SYNC
Route planning, flight sync and the web app. We read the database.
CHECKING…
30 days ago90 days agoNo uptime data yetTodaySIGN-IN
Signing in. We fetch the keys that verify sign-in tokens.
CHECKING…
30 days ago90 days agoNo uptime data yetTodayOFFLINE MAPS
Offline map downloads. We read the current dataset's manifest and map archive.
CHECKING…
30 days ago90 days agoNo uptime data yetTodayAPP UPDATES
Over-the-air app updates. We ask the update server for an update.
CHECKING…
30 days ago90 days agoNo uptime data yetTodayLIVE MAPThird-party
The online base map in the app, served by OpenFreeMap. We fetch its tile index.
CHECKING…
30 days ago90 days agoNo uptime data yetToday
How we check
Our servers use each service the way the app does: they read from the database, fetch the sign-in keys, download the offline map manifest and index, ask the update server for an update, and load the live map's tile index. The live status refreshes about once a minute, and a check is recorded in the history every 15 minutes. A check that takes longer than 2.5 seconds counts as slow, and one that takes longer than 5 seconds fails.
One failed check shows as degraded. Two in a row show as a partial or major outage, and it takes two good checks in a row to show the service as working again. Uptime counts a major outage in full and a partial outage as 30% down. Each daily bar shows that day's worst state. "No data" means we have no checks for that day, not that the service was up.
LIVE MAP is run by a third party (OpenFreeMap). We report it here because the app uses it, but we cannot fix it.
The same data as JSON: /api/status and /api/status/history.