Sign in →

Incident Manager

Declare, track, and resolve incidents with timeline updates, postmortems, and automatic status page publishing.

Updated 2026-07-29Suggest edits

Incident Manager

Incident Manager is the operator's tool for declaring, tracking, and resolving service disruptions. Every incident is published to your public status page in real time.

Incident Severity

SeverityColorMeaning
LOWYellowDegraded performance, minimal customer impact
MEDIUMAmberModerate impact to a subset of customers
HIGHOrangeSignificant impact to many customers
CRITICALRedFull outage or widespread customer impact

Incident States

INVESTIGATING → IDENTIFIED → MONITORING → RESOLVED → CLOSED
StateMeaning
INVESTIGATINGRoot cause not yet known
IDENTIFIEDRoot cause known, fix in progress
MONITORINGFix deployed, watching for stability
RESOLVEDFully resolved. No ongoing customer impact.
CLOSEDIncident archived after resolution.

Declaring an Incident

  1. Go to Operations → Incident Manager
  2. Click + Declare Incident
  3. Enter title, severity, and affected services
  4. Add an initial update describing what's known
  5. Click Declare — the incident is immediately visible on your public status page
⚠

Declaring an incident updates your public status page immediately. Use severity LOW for internal investigations you don't want to alarm customers about until confirmed.

Timeline Updates

Add updates throughout the incident lifecycle:

  • Each update is append-only (immutable audit trail)
  • Updates appear on the public status page with timestamps
  • Subscribers receive notifications via email and webhook

Auto-Detection

Aforo can automatically create incidents when uptime monitors detect prolonged downtime. Configure auto-incident rules:

  • Minimum downtime duration before auto-declaring (e.g. 5 minutes)
  • Which monitors trigger auto-declaration
  • Default severity for auto-detected incidents

Postmortems

After resolving an incident, write a postmortem:

  • What happened — timeline of events
  • Root cause — technical explanation
  • Impact — which customers, for how long
  • Remediation — what was done to fix it
  • Prevention — what changes prevent recurrence

Publish the postmortem to make it visible on the status page.

Scheduled Maintenance

Announce planned downtime before it happens:

  1. Go to Operations → Incident Manager → Maintenance
  2. Click Schedule Maintenance
  3. Set start/end time and affected services
  4. Subscribers are notified automatically 24 hours before

Scheduled maintenance appears on the status page and prevents false-positive incident alerts during the window.

Status Page Integration

Every incident and maintenance window is visible on /status. Customers who subscribe receive:

  • Email notification when incident is declared
  • Email notification when incident is resolved
  • Webhook payload on every state change (for PagerDuty, OpsGenie integration)