Status
degraded

What this page checks

Every 30 seconds the page calls a public health endpoint on the API. That endpoint does not just answer “yes” — it verifies that the database accepts a query, that Redis responds, and that the scan queue is reachable, then reports the worst of those. So operational here means the pipeline that runs your audit is actually able to run it, not merely that a web server is listening.

The four components

Web frontend

The site itself. If this is down you are not reading this page.

API server

Handles scans, accounts, billing and every data request the site makes. A degraded API usually shows up as scans that queue but never start.

Scan worker

The process that actually fetches and renders your page and runs the audit modules. It is the slowest link by design — a full audit renders a real browser — so a backlog here means longer waits rather than failures.

Cache layer

Redis, holding sessions, the scan queue and recent results. If it is unavailable, scans cannot be queued at all, which is why it counts toward the overall status.

If something looks wrong

A scan that sits at “queued” for more than a couple of minutes while this page says everything is fine is worth reporting — it usually means one audit module is stuck on a particular site rather than the platform being down. Include the URL you scanned; that is almost always enough to reproduce it.