Incidents and maintenance
The incident timeline - five renamable states with fixed icons and colors, an impact axis, per-update component statuses, templates, and scheduled maintenance.
Incidents and maintenance
Incidents are posted from the page editor's Incidents tab and render as a timeline on the public page. Each incident has a title, an impact level, a current state, and one or more updates over time.
Incident states
An incident moves through five states. The labels are renamable per page; the colors and icons are fixed so the timeline reads consistently:
| State | Default label | Color |
|---|---|---|
investigating | Investigating | amber |
identified | Identified | orange |
in_progress | In Progress | blue |
monitoring | Monitoring | cyan |
resolved | Resolved | green |
Each state has its own glyph on the public timeline (a magnifier for Investigating, a target for Identified, an activity pulse for In Progress, an eye for Monitoring, a check for Resolved).
Impact
Independently of state, an incident has an impact: none, minor, major, or critical. Impact colors the incident on the public page so visitors can gauge severity at a glance.
Posting updates
Each time you post an update you:
- Write the update text.
- Move the incident to a state.
- Optionally set the status of one or more affected components.
The public timeline appends the update instantly. When you move an incident to Resolved, every component the incident touched is auto-reset to operational, which also closes out its contribution to the uptime history.
Templates
Save reusable incident templates (a default title, body, state, and impact) so you can spin up a common incident - "API degradation", "Scheduled DB maintenance" - in one click.
Scheduled maintenance
Maintenance is a special incident kind with a scheduled start and end window. It renders in a dedicated "Scheduled Maintenance" section on the public page, separate from active incidents.