Status page incidents and maintenance

Incidents and scheduled maintenance reach your status page from On-Call. You run the incident or the maintenance window in On-Call, and the status page shows it to visitors and keeps it in step. This page explains what gets published, how it stays up to date, and what visitors see.

#Publish an incident

The public impact decides how the affected components look while the incident is open: Minor shows them as Degraded Performance, Major as Partial Outage, and Critical as Major Outage. None shows the incident without changing any component's color.

Subscribers who follow the affected components, or the whole page, get an email. See Subscribers.

#Keep a published incident up to date

Once an incident is published, On-Call keeps the status page in step:

Each update is emailed to the incident's subscribers.

To take an incident off the page, click Unpublish next to the On status page badge and confirm.

#Publish a postmortem

After an incident is resolved, you can write a postmortem in On-Call with the Postmortem button on the incident. Save internal keeps it private. Publish publicly shows it under the incident on your status page. You can unpublish it later.

The status page's Incidents tab shows a Postmortem badge on incidents that have one.

#Record a past incident

You can publish an incident that has already been resolved, for example one you handled before you had a status page. Use Publish to status page on the resolved incident as usual.

A past incident:

• appears on the days it actually happened, in the uptime bars and the incident calendar
• is marked Past in the status page's Incidents tab
• does not email any subscriber

#Schedule maintenance

When a window with a description is published to a status page, its subscribers get an email.

#What visitors see

• Before it starts: a "Scheduled maintenance" notice near the top of the page when the start is within the next 7 days. The window also appears in the incident calendar.
• While it runs: the affected components show Maintenance, and the window is listed at the top of the page. This happens automatically between the start and end times.
• After it ends: it moves to the page's history.

#Update or finish maintenance

Open the window under On-Call → Maintenance:

• Post update adds a timeline update. It appears on the status page and is emailed to subscribers.
• Edit changes the title, description or schedule, for example to extend a window that is running long.
• End now (while it runs) or Mark completed finishes it. The status page adds a closing update, "This maintenance has been completed."

#What visitors see

The public page shows incidents and maintenance in a few places:

• The banner and the top of the page: the overall status, and anything happening now listed by name.
• Components: affected components take the incident's or maintenance's color, as described above.
• Incident & Maintenance Calendar: a month-by-month calendar of incidents and maintenance across the page's history window, with each one's updates and, if published, its postmortem.
• Permalinks: every incident and maintenance window has its own address, /incidents/<id> or /maintenances/<id> on your status page domain. Emails to subscribers link there.

On a page that uses A page per group, each group's page shows only the incidents and maintenance that affect that group's components.

#Related

• Alerts and incidents in On-Call
• Components and groups
• Subscribers
• Silence windows