Developers
Live monitoring coming laterService status
A live public status page with uptime history is planned but not built yet. This page tells you honestly how health is tracked during beta and how to self-diagnose.
How health is monitored today
During beta, service health is monitored through the hosting providers' deployment and runtime logs — the API on Vercel, the database and storage on Supabase, and the capture worker on its own service. There is no automated public uptime feed yet, so this page intentionally shows no live indicators.
No live data on this page
Anything resembling an "all systems operational" banner here would be static text, not telemetry — so we do not show one. A real status feed is on the roadmap.
Self-diagnosis
Most incidents show up in one of three ways.
- Captures stuck in queued — the capture worker is likely not running or cannot reach the database. Requests are safe and will process when the worker recovers.
- 5xx responses — a deployment or configuration problem on the API. Retry with backoff; persistent errors are on our side.
- Signed URL fetch failures — usually an expired link rather than an outage. Re-request the status endpoint or refresh the link from the capture's detail page.
The full error guide lives in the documentation.