Status
Is the service up?
This page asks the health endpoint from your own browser, so what you see is what your systems would see. No status is cached and nothing here is a dashboard we curate.
Live check
The health endpoint, right now
Checking…
With JavaScript disabled, open /healthz directly: a 200 with status “ok” means up.
The check runs when this page loads.
- 200 with status “ok”
- The service answered and completed a real round trip to its database before saying so. A green here is not a self-image.
- 503
- The database is unreachable, or the authorisation service has refused the ledger’s own credential. Either way, every request will fail and the fault is on our side, not in your key.
Records
Where problems are written down
Incidents
No incident history is published yet. When one occurs it will be recorded on the changelog with what happened and what changed.
Defects
Every defect found by an audit round is on the audit history, with its status.
Changes
Capabilities, fixes and operations changes are dated on the changelog.
Monitoring probes should use HEAD /healthz; it answers exactly as GET does, with an
empty body.