Automatic Incident Management

StatusPage.me can handle the full incident lifecycle for you — creating an incident the moment a monitor goes down, notifying your subscribers, and resolving it automatically when the monitor recovers. No manual intervention required.

These three automation settings work together and are configured per status page.

The Three Settings

Auto Incidents

When enabled, an incident is automatically created on your status page whenever a monitored component transitions to a DOWN state.

The incident is created with:

• A title derived from the component name (e.g., “API Gateway is experiencing issues”)
• A status of Investigating
• The affected component linked automatically

Without this setting, you must create incidents manually every time a monitor goes down.

Auto Incident Notify

When enabled alongside Auto Incidents, all status page subscribers are immediately notified as soon as the incident is created.

Notifications are sent via every channel your subscribers have configured (email, Slack, webhooks, etc.).

Note: Auto Incident Notify has no effect if Auto Incidents is disabled — there is no incident to notify about.

Auto Resolve

When enabled, the incident is automatically resolved as soon as the monitor returns to an UP state.

The incident is updated to a status of Resolved with a timestamp matching the recovery. Subscribers receive a resolution notification if Auto Incident Notify is also active.

How They Work Together

Here’s a full timeline when all three settings are active:

You can use any combination:

• Auto incidents only — creates incidents silently (no subscriber alerts)
• Auto incidents + notify — creates and broadcasts instantly
• All three — fully hands-off lifecycle management

Plan Availability

How to Enable

1. Go to your Status Page dashboard
2. Open Settings → Incidents
3. Toggle the settings you want to enable
4. Save

Changes take effect immediately for future monitor state transitions.

Manual Overrides

Automation doesn’t remove control. You can still:

• Edit an auto-created incident (change title, add update messages, change severity)
• Manually resolve an incident before the monitor recovers
• Suppress auto-creation for a specific monitor by temporarily pausing it

If you manually resolve an incident before the monitor recovers, Auto Resolve will not re-open it when the monitor eventually returns UP — recovery is treated as a no-op if no open incident exists.

Related

• Incident Templates — pre-write incident messages for common issues
• Runbooks — attach response playbooks to incidents
• Notification Channels — set up where alerts are delivered