voar status
Check the services and how long jobs take to start.
Reading voar's status
How we decide
Each check has a rule written in voar's code. The numbers below are the ones the server uses.
The three states
- Operational
- The check passed.
- Degraded
- It works, but with a problem that may delay jobs.
- Down
- The check failed or got no answer.
The rules
- API
- The API answers this request and reads the database. Down if the database doesn't answer.
- Job launcher
- The process that starts machines sends an update each minute. Operational when the last update is under 2 minutes old, degraded from 2 minutes to 3 minutes, down at 3 minutes or with no update.
- Sign-in
- voar asks the sign-in service about a made-up token. If it refuses the token, that counts as an answer. Down if it gives no answer or a server error.
- Queue
- Counts the jobs waiting for a voar machine. Degraded when the oldest has waited more than 5 minutes. Jobs waiting for credit or for their organization's own limit are not counted.
- Machine capacity
- Compares the vCPUs of the machines that are on with the most voar runs at once. Degraded only when all are in use and a job is waiting.
- GitHub webhooks
- Shows how long ago the last GitHub event arrived. This does not set a status: an hour without jobs is not an outage.
- Time to start
- The time runs from the moment GitHub queues the job to the moment the runner starts, so it includes starting the machine. It is the median (p50) and the p90 over the last 24 hours, rounded up. With fewer than 10 jobs, no number is shown.
If the database doesn't answer, the API, the queue and the capacity are down, and the start time and the failures are not shown.
The page asks again every 30 seconds while the tab is open. A hidden tab doesn't ask.