Service status.
Live from the platform's own health checks.
Checking Cordon Cloud
This page reports the service you reach from here.
Service objectives
| Component | What it is | Target |
|---|
| Ingest API | signed results from CI and runners | 99.9%, p95 under 2 s per upload |
| Console and API | the dashboard and its API | 99.9%, p95 page under 1.5 s |
| Alert delivery | Slack, Teams, Jira, PagerDuty, webhooks | 99.9%, p95 under 60 s |
| CLI sign-in | cordon-scanner login device flow | 99.9%, never needed to gate a build |
| @cordon assistant | in the console | best effort, never affects scanning |
Targets, not a record. Uptime history is published here once it has been measured, not before.
If Cordon is down, what happens to you
| Failure | Impact on you | What the system does |
|---|
| Cordon Cloud down | none for gating | The CLI gates locally with cached policy and its bundled intel. Uploads retry, or are saved as CI artefacts. |
| Policy bundle unavailable | defaults apply | Never looser than your repository file plus Cordon's defaults. |
| Slack, Jira or PagerDuty down | alerts delayed | Retries, then the dead-letter queue shown in the console. Findings are never lost. |
| Your Cordon Runner offline | scheduled scans pause | A coverage gap is raised after the scheduled scan is missed. |