Documentation · Help
The status page
What runners.io/status shows for the runners and Terraform runs, how a check reads Unknown rather than Operational, and what the page does not show.
runners.io/status answers one question without signing in: is the problem yours or ours?
Two components, each with its current health:
| component | checked by |
|---|---|
| GitHub Actions runners | the CI engine's readiness check, which includes its database |
| Terraform runs | the Terraform engine's health check, which includes its database |
Each reads Operational, Maintenance, Degraded, Outage or Unknown. A live check that gets no answer, or answers that the engine is not serving, reads Outage. A check we could not run reads Unknown, never Operational: a status we cannot read is not a status we report as healthy.
Below them is every incident a person on our side has posted in the past 90 days, with its impact (Degraded performance, Outage or Maintenance) and its updates (Investigating, Identified, Monitoring, Resolved).
Your own jobs. A job that waits because of its label, your card, your concurrency limit or your spending cap says so on its own page; troubleshooting has where to look.
Uptime figures or response times. We do not publish an uptime percentage.
Anything that would help somebody attack us. A check keeps only the HTTP status code it got back: no hostnames, addresses, metrics or queue lengths.
The page reads the engines at most once a minute, and says how old its reading is. It is served by the same application as the dashboard, so if the status page itself does not load, that is an answer too: email us.