⌘K
Incident Lifecycle
Incidents track the full lifecycle of an outage or degradation — from detection to resolution. They can be created automatically from monitor failures or manually by any team member.
Every incident moves through a defined set of statuses:
| Status | Meaning |
|---|---|
| Draft | Incident created but not yet declared. Allows teams to assess before notifying stakeholders. |
| Investigating | Team is actively looking into the issue. Escalation timers begin if an escalation policy is attached. |
| Identified | Root cause found. Responders are working on a fix. |
| Monitoring | Fix deployed. Team is watching to confirm stability before closing. |
| Resolved | Incident closed. Duration is calculated automatically from declared_at to resolved_at. |
Each incident carries linked monitors, severity, tags, and a timeline of updates. Status page subscribers are notified automatically when an incident is published.