Status
We promise the order check API answers at least 99.5% of the time each calendar month. Every 5 minutes we read each address below once, and this page counts what came back.
Now
| Address | Last reading | This month, our readings | This month, outside monitor |
|---|---|---|---|
| Order check API | Answering, 2026-11-21 02:12:24 UTC | 100.00% | 100.00%, answering |
| Sandbox | Answering, 2026-11-21 02:12:24 UTC | 100.00% | 100.00%, answering |
| Website, app and MCP | Answering, 2026-11-21 02:12:24 UTC | 100.00% | 100.00%, answering |
Our own readings are taken from our own hosting, so if the whole platform goes down they stop; they also check that the API and the sandbox can reach their data. The outside monitor is UptimeRobot, which checks from outside our hosting that each address answers.
The rules every answer reads from were built 2026-11-20 17:02:33 UTC. The nightly reading of state and federal sources last started 2026-11-20 17:29:29 UTC and finished 2026-11-20 17:29:42 UTC.
The last three months
Expected is one reading every 5 minutes since we started measuring on 2026-11-20 06:47:14 UTC. A reading that never arrived counts as not answering.
| Month | Address | Answered | Readings expected | Readings received |
|---|---|---|---|---|
| 2026-11 | Order check API | 100.00% | 241 | 241 |
| 2026-11 | Sandbox | 100.00% | 241 | 241 |
| 2026-11 | Website, app and MCP | 100.00% | 241 | 241 |
Incidents
None recorded since we started measuring.
What counts as answering: the API and the sandbox answer 200 from their status address and can reach their data; the website answers 200 from its health address. An order we could not check is still answered, never held: how that reads.