Status
Service disruption
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
No response (Could not reach the API: fetch failed)
not responding
Data coverage
50 of 60 jurisdictions fully ingested
operational
Usage, last 7 days
223 MCP tool calls, plus 5565 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.