Status
This page is served by the website, which is deployed separately from the solving gateway. That is deliberate: a status page served by the failing system reports nothing during the outage it exists for.
Last checked 2026-08-24 15:47 UTC, 9s ago. Checks run in the background on a fixed interval; rendering this page does not contact the gateway, so the page cannot be slower or less available than what it is reporting on.
What each state means
| State | Meaning |
|---|---|
| Operational | The gateway answered its health check. Tasks are being accepted and solved. |
| Degraded | The gateway answered and reported a problem of its own — usually a solving vendor failing over, which callers see as slower solves rather than errors. |
| Unavailable | The gateway did not answer within the check's budget. Submitted tasks are likely failing. Your balance is unaffected — it is debited per solve, and a solve that did not happen is not charged. |
| Unknown | No check has completed yet, usually because this site has just restarted. Reported as unknown rather than as the last thing that happened to be true. |
Machine-readable
The same reading is available as JSON at /status
with Accept: application/json, for an
external monitor that should not have to scrape this page.
Incidents
There is no incident history here yet. When there is one it will be written by hand, after the fact, and will say what happened rather than that we experienced elevated error rates.
Something wrong that this page does not show? Support.