Skip to article
Incident response

How incidents open and resolve

Follow a confirmed outage and add useful public context.

1 min read

From failed check to incident

The first failed check starts confirmation. If the second check 30 seconds later also fails, Cheapmonit opens an incident, queues notifications, and updates published components. Repeated failures stay in that incident.

A successful check during an outage starts recovery confirmation. A second success closes the incident and records its duration.

Share an incident note

  1. Open Incidents and find the affected monitor.
  2. Select Add public note or Edit public note.
  3. Describe the customer impact and current response in up to 500 characters.
  4. Save the note. It appears on the status page and incident feed, so keep private addresses, credentials, and internal errors out of it.

Find past incidents

Filter the latest 200 incidents by monitor and ongoing or resolved status. The failing check’s cause remains in the private dashboard; public pages show the note and incident timing.

Pausing a monitor keeps an existing incident open. Incident creation and resolution are automatic; manually created incidents and postmortems are not supported.