Skip to main content
The incidents view in the dashboard
An incident records that something is wrong. A monitor opens one when it fails past its threshold, and you can open one by hand for an issue a check can’t see. Either way it shows on the status page and starts escalation.

​
Open one by hand

  1. Go to Incidents → New.
  2. Set a title, the affected component, and the impact.
  3. Post an opening update.
The component reflects the incident’s impact on the status page, and the page stops claiming everything is operational.

​
Post updates

Each update has a status: investigating, identified, monitoring, or resolved. Subscribers and the page’s feed get every update. Resolving the incident clears it from the page’s active list and returns the component to operational.

​
Draft with AI

The update composer has a Draft with AI option when an API key is configured. It writes an update from the incident’s context, stating what’s known and making no promises. Nothing posts until you review it, and the “AI-drafted” badge clears as soon as you change the text or the status.

​
Acknowledge

Acknowledging an open incident stops its escalation ladder. See Escalation & on-call.

​
Postmortems

After an incident resolves, write a blameless postmortem on it: what happened, the impact, and what you’re changing. It stays on the incident and can show in the public history.

​
Timeline

Each incident keeps a single timeline of its lifecycle: opens, updates, who acknowledged, and the escalation steps that fired, in order.