Status · checked live, from your browser
Service status
Each line below is checked now, by your browser, against the live API. Nothing on this page is typed in by us, so it cannot say “all systems operational” while something is down.
Right now
What answered, and what it said
| Check | Result | Detail |
|---|---|---|
| API | checking… | |
| Quote ledger reachable from the API | checking… | |
| Signed ledger head | checking… | |
| Signed evidence-log head | checking… | |
| Running build | checking… |
What “degraded” means here. If the ledger cannot be reached, quotes are
still priced but nothing is recorded, and every response says recorded: false. We
never report a record that was not written. That is the designed safe state, not a hidden one.
History
No uptime history yet
An uptime percentage is only honest if something outside our own systems measured it. No external monitor has been running long enough to give one, so this page shows none, rather than a number we did not measure. When a monitor has three months of data, its history will be linked here.
Incidents and anything that affected recorded evidence are written up on the changelog. How we would recover from losing the database, and when we last proved it by restoring a backup, is on the continuity page.
Dependencies
What we depend on, and their own status pages
| Provider | What stops if it stops | Their status |
|---|---|---|
| Cloudflare | The site and the API | cloudflarestatus.com |
| Supabase (Frankfurt) | Recording; pricing continues and says so | status.supabase.com |
Evidence you have already saved does not depend on either: an export, a proof or an attestation verifies offline, with no call to us. How to check one.