Status
All systems operational
Checked just now, against the live API — this page is never cached. A status page served from cache reports health it did not measure, which is how an outage here went unnoticed for hours on 2 August 2026.
REST API
Database reachable · responded in 146 ms
operational
Data coverage
50 of 60 jurisdictions fully ingested
operational
Capacity
- Connections in use
- 3 / 50
- Pool saturation
- 6%
- Requests in flight
- 2 / 32
- Requests shed (lifetime)
- 0
Published because the failure that took this service down was a capacity failure, not a crash: it kept returning HTTP 200 the whole time. Sustained saturation near 100% is the signature.
Usage, last 7 days
335 MCP tool calls, plus 4630 from our own uptime monitor, which are excluded from that figure.
Published unflattering. Counting connections instead of calls, or leaving our own monitor in the total, would make this number look far better than it is.
Per-jurisdiction ingestion detail is on the coverage page. Known limitations are in the changelog.