Incident Response

When a monitor detects an outage, an “incident” is created. This guide explains the incident flow and how to respond.

Incident Lifecycle

1. Detection: after 5 consecutive failed checks, an incident is created automatically and your notification channels are notified (a single failure never notifies)
2. Acknowledge (optional): pressing “Acknowledge” sets the status to acknowledged, signaling to your team that someone is on it
3. Resolution: when the monitor recovers, the incident is resolved automatically and a recovery notification is sent. You can also resolve manually

See the monitoring lifecycle for the exact detection rules.

Viewing Incidents

The “Incidents” tab on the service detail screen (click a service card) lists that service’s incidents.

Status	Meaning
Ongoing (red)	Outage in progress
Acknowledged	Someone is handling it
Resolved	Recovered

Note

Resolved incidents are deleted automatically after your plan’s retention period. Ongoing and acknowledged incidents are never deleted (see data retention).

Manual Incidents

You can record incidents independently of automatic detection — useful for user-reported outages or components outside monitoring that should appear on your status page.

1. On the service detail’s “Incidents” tab, press “Create incident”
2. Enter a title and register (it gets a “Manual” badge)
3. Press “Resolve” once handled

Manual incidents stay open until resolved manually, and only manual incidents can be deleted.

Warning Incidents (degraded)

When SSL certificate or domain checks cannot be completed due to a problem on the checking infrastructure side, a warning incident (severity: warning) is created, distinct from a normal outage. Since the target itself may be fine, verify the certificate or domain status separately.

When Notifications Don’t Arrive

• If a monitor has channels attached directly, team-wide channels are not notified (see notification behavior)
• Rapid down/up cycling triggers flap suppression, pausing notifications (incidents are still recorded)
• During maintenance windows, incident detection itself is suspended
• Check the integrations settings for unverified (email) or disabled channels