Status Codes
Learn what the status values that appear in the dashboard and API mean.
Site Status
| Status | Meaning | When is it seen? |
|---|---|---|
| Working | The site is accessible and the decision engine sees no errors. | If the frontend probe is successful; if there is no heartbeat or if it is up. |
| Offline | Interruption or serious error detected. | 5xx, network error, two probe failures or down+unknown combinations. |
| Degraded | There is partial corruption; the site may not be completely down. | For example, if the frontend is up but the heartbeat is down or if the frontend is blocked while the heartbeat is up. |
| Unknown | The system did not receive enough reliable data to make a decision. | If both probes return unknown or the first check has not yet arrived. |
| In care | Maintenance_active is opened in the panel. | Maintenance mode is a separate panel state that overlaps the normal site status. |
HTTP Response Code Behavior
- 2xx and 3xx responses are accepted up. Secure HTTP client redirects follow a maximum of 3 steps.
- Generic 4xx responses are up because the site is accessible. However, if there is a fatal error in the WordPress layer, the plugin transmits this via heartbeat and is marked as down.
- 403 content is classified as unknown if it has a WAF/challenge signature.
- 5xx, 520-527 Cloudflare origin errors and network/dns connection problems are counted down.
- If the 503 response has an X-AU-Maintenance header, it is marked with reason_type=maintenance.
Probe Based Status
Check records store the frontend_status and heartbeat_status fields separately, while the API /status endpoint returns only the combined site status information. See the decision matrix on the Overview page for combination rules.
Jump to Overview for details of the decision matrix.