Status

Is the gate up?

These checks run in your browser, against production, when you load this page. Nothing is cached and nothing is reported by us — you are reading the same endpoints our own monitoring reads.

Checking…

What each one means

Control plane
The API is running and serving. If this is down, begin and report are unreachable — your agent gets a connection error, which is the safe failure: no decision means no permission to act.
Readiness
The API can reach its database. A gate that cannot write cannot promise at-most-once, so it refuses rather than guessing.
Lease expiry
The worker is running. This is the one that fails quietly: if leases stop expiring, effects sit at pending for ever and every retry is answered in_flight — while every other check on this page stays green. It is the failure we watch hardest.

The honest limitation of this page

A status page served by the thing it reports on cannot tell you the thing is down. If Ratchet is unreachable, so is this. That is why it is not the only monitor: an external service probes production on a schedule from outside our infrastructure, and Fly's own health checks restart an unhealthy machine every 15 seconds.

Machine-readable

Point your own monitor at these. They need no credential and return JSON.