Update or edit an incident
Incidents are your manual way of communicating outages, disruptions, or maintenance for custom monitors. Once created, you can add updates, adjust incident details, or even correct typing errors—all without overwhelming your subscribers.
Add an incident update
To share progress or resolution steps:
Navigate to Incidents from the left menu.
Open the ongoing incident and click the Add update button (or use the 3-dot menu → Add update).
On the update form, you can adjust:
- Incident phase– Click to select one of these stages:
- Investigating – When you’re actively checking the issue
- Identified – Root cause located
- Monitoring – Fix implemented and being observed
- Resolved – Issue fixed and services are restored
- Severity – Update to Major, Minor, or Maintenance as the situation evolves
- Update details – Provide current status or next steps
- Update time – Defaults to the current time; customize as needed
- Affected monitors – Mark changes to monitor status (e.g., from Down to Up or Warn)
- Notify subscribers – Optionally check to send alerts about this update
- Incident phase– Click to select one of these stages:
Click Publish update to post the changes.
Tip: If all affected monitors are up again, set phase to Resolved—this will automatically return their status to Up.
Edit existing incident details
To fix typos or minor inaccuracies without sending fresh alerts:
Open the incident via the Incidents list, then click View details.
To rename the incident:
- Click the pencil icon next to its name.
To edit an update in the incident timeline:
- Click the pencil icon next to the update entry.
- Make adjustments to the update’s phase or text.
Click Save once finished.
Edits made this way do not trigger notifications to subscribers.
Remove an incident (permanent)
If the incident was created by mistake or no longer applies:
Go to the Incidents list.
Click the 3-dot menu (⋮) next to the incident.
Select Remove Incident, then confirm deletion.
Warning: This action is irreversible. All data associated with the incident—including history—is permanently deleted.
Instead, consider changing the phase to Resolved to retain a record while clearing the ongoing list.
Best practices for incident updates
- Keep titles concise and descriptive (e.g., Checkout API not processing payments).
- Move through phases logically—from Investigating to Resolved—as you progress.
- Use updates to inform users of real progress (e.g., “We identified the issue”).
- Always resolve incidents to signal closure and restore trust.