Viewing incidents
Dashboard
The Dashboard shows active incidents on the overview page with severity, affected monitor, duration, and affected regions. Click an incident to see its full timeline, check results, and update history.CLI
-o json output to jq, or use the API’s status query parameter (below).
API
Creating manual incidents
For issues that aren’t caught by automated monitoring:Resolving incidents
Automatic resolution
Most incidents resolve automatically when the monitor recovers. The recovery policy controls this:- The monitor must pass a configurable number of consecutive checks (default: 2)
- A configurable number of regions must be passing (default: 2)
- After resolution, a cooldown period prevents the same monitor from immediately re-opening a new incident (default: 5 minutes)
Manual resolution
Updating incidents
Incident severity is set at creation (or by trigger rules for automated incidents) and can’t be changed directly. To add context to an active incident — for example, to note that a full outage has degraded into a partial one — post a timeline update via the API:Incident timeline
Each incident tracks a timeline of events:- Created — initial detection with trigger rule and affected regions
- Severity changed — escalation or de-escalation
- Resolved — automatic recovery or manual resolution
- Reopened — monitor failed again after resolution
Maintenance windows
Schedule maintenance to suppress alerts during planned downtime:Next steps
Alerting guide
Configure how your team gets notified about incidents.
Monitors guide
Fine-tune incident policies per monitor.