Status Page Incidents

Incidents are created on your Status Page to help convey the state of downtime events to your userbase in real-time. Incidents hold the chronology of an event, from start to finish with every change in status in between. Each incident can be in one of the following statuses:

• Investigating
• Monitoring
• Identified
• Maintenance
• Notification
• Resolved

There are several ways to add Incidents:

• Click Status Pages > All Status Pages to display the All Status Pages view. Locate the desired Status Page and click More Actions > Add Incident:

• While managing the Status Page, click the Incidents tab then click + New Incident:

• Click Status Pages > Incidents to display the All Incidents view. On this page, click + New Incident:

Incident Fields

Return to top

Starts/Ends: 

Date and Time of incident start. Leave blank to start the incident when this form is saved.

Date and Time of incident end. Leave blank if the incident is ongoing.

It is possible to backdate incidents, in case you need to acknowledge downtime retroactively. 

Please note: Incidents are rounded to the nearest minute. (i.e. 15 seconds and 35 seconds of incident downtime will both display <1 minute, while 9 minutes 59 seconds will be 10 minutes.) The start and end date of an incident cannot be in the future.

This incident should count as downtime: This incident’s duration will contribute to global downtime calculations.

Note that there are some scenarios where downtime will still be counted when this option is unchecked. These scenarios will occur based on the selection of the Uptime calculated by setting:

• Scenario 1: Check-Based Component Uptime and option is unticked: When this option is selected, downtime will still be counted.
• Scenario 2: Incident Durations and option is unticked: When this option is selected, downtime will not be counted.
  
   

Components Affected: OPTIONAL: Select the component(s) affected by this incident. You can also select the status to change for the component, such as Degraded Performance or Major Outage.

There is also an option to Update selected component(s) with the above status(es) when this form is saved.

Note: the update will only come into effect once the incident’s start date and time commences.

To review the REST API Endpoints for the incidents, please click the link here: https://uptime.com/api/v1/docs/#/statuspages

Incident Status and Status Updates

Select an incident state, and provide an optional incident description. Markdown is supported for complex formatting. Use double-spacing to begin a new line. Use the Preview button to review your incident description.

When an incident is Created, Updated, or Resolved, users have the option to Notify Status Page Subscribers of this Update. There is a delay of two minutes before the update is sent when notifying subscribers of an update to your status page.

When an incident is Resolved, users can Reset all affected components to Operational. 

When updating an incident, you can choose from the following set of predefined statuses to communicate the current progress in your investigation and resolution of the issue. Suggestions on how to use each Incident Status are as follows:

Overview of Your Incidents

In addition to the incident list that is displayed under the Incidents tab when managing a specific Status Page, you can also view all current and previous Incidents across all your Status Pages by navigating to Status Pages > Incidents:

This page displays all incidents along with some features that allow you to get a quick overview of your incidents, manage multiple incidents on multiple pages, and update their status:

• Summary cards for Total Active Incidents, Investigating, Monitoring, Identified, Maintenance Enabled, and Resolved. Click the card to view all incidents with that status.
• Status Page column that displays which status page is connected to each incident.
• An Update column that displays the most recent status update to the incident.
• The Start and End date and time of the incident.