System status
The Nebbos platform status is published on the live status board at status.nebbos.ai . This reference specifies the surfaces monitored, the incident lifecycle, the historical-uptime methodology, and the subscription options.
Live status surface
The live status board surfaces the current health of each user-visible surface:
- REST API
- MCP endpoint
- WebAuthn ceremony
- Cradle attestation
- Export pipeline
- Audit-chain verification
- Per-region data plane
Colour codes: green (nominal), yellow (degraded, investigation active), red (incident declared).
Incident lifecycle
| Phase | Substrate behaviour |
|---|---|
| Declared | Substrate telemetry or a synthetic probe fires an alert. The incident is declared and posted to the status board within five minutes, naming the affected surface, observed impact, and estimated blast radius. |
| Updated | Recurring updates every thirty minutes for Sev-1 and hourly for Sev-2 until resolution. Each update states the change since the previous update. |
| Mitigated | Operational impact ceases. The incident remains on the board with the mitigation identified. Root-cause investigation may continue. |
| Resolved | Root cause identified and remediation applied. The incident closes with a link to the postmortem placeholder. |
| Postmortem | Every Sev-1 and Sev-2 incident produces a blameless postmortem published within seven days of resolution, containing a five-whys analysis and corrective actions with named owners and dates. |
Historical uptime
- Ninety days of rolling per-surface uptime, updated hourly, on the live board
- Twelve months of incident summaries listed on the board with per-incident postmortems linked
Uptime is computed against the synthetic-probe methodology specified in SLA.
Subscriptions
RSS, JSON, and email-digest subscriptions are available from the live board. High-severity event subscribers receive notifications within two minutes of declaration.