Service status
Degraded
Something is slower or more limited than it should be. What and how much is in the table below.
Measured when you loaded this page, at . Nothing on it is set by hand.
Components
What is working
| Component | State | Detail |
|---|---|---|
| Website and API | Operational | Serving requests. You are reading a page it generated. |
| Database | Operational | Responding in 9 ms. |
| Scan queue | Operational | Empty. Nothing waiting. |
| Scheduled maintenance | Operational | Last run completed normally. |
| Report email | Degraded | Sending is switched off. Reports are still generated and readable in your account. |
| Billing | Operational | Checkout and subscriptions are working. |
Scanning
Did scans finish
No scans have run in the last seven days, so there is no rate to report. An empty figure here is not a fault.
A scan counted as failed here is one our scanner could not finish. It does not mean the page being tested had problems. If your scan failed, that is our fault and not a finding about your site.
Incidents
Open problems
None recorded.
Counts only. The messages themselves stay private, because an error is as likely to contain a customer's URL as anything else.
For build pipelines
Telling an outage apart from a real finding
If the GitHub Action sent you here, it is because your build failed for a reason that was
not an accessibility issue. The Action reports those separately: a
status of service-error or
timeout means us, and never your site.
Anything that polls can read /status.json, which returns the same measurements this page shows.