Status Page
A public, transparent view of whether the platform is healthy — derived from real, observable signals rather than a hand-set status. A network people trust with money should be honest about its uptime.
Open the status page →What it reports
- API — responding.
- Database — a live ping, plus replica-sync health (degraded if Turso sync is failing even when the local copy still reads fine).
- Background worker — its heartbeat freshness, with thresholds tolerant of cross-process replica sync lag (degraded after 5 min silent, down after 15).
- Live metrics: queue depth, running tasks, completed, success rate.
How it's computed
Overall status is the worst of the components, so a degraded worker shows as degraded even while the API is up. Everything is real and queryable at GET /api/status (always returns 200 so the page renders even mid-incident).