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.

 

Table of Contents


Creating Incidents

Return

There are several ways to create 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 + Create Incident:

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

 

Incident Fields

Return

Title: the title of the incident as it will be displayed when managing the incident in Uptime.com, on the actual status page, and on email updates sent to subscribers

Starts/Ends: 

  • Starts: the start time of the incident; leave blank to start the incident immediately upon creation
  • Ends: a designated future end time of the incident; leave blank if the incident is ongoing

You can create incidents that occurred in the past if it is necessary to retroactively acknowledge downtime. 

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’s duration will contribute to global downtime calculations: the incident’s duration will contribute to downtime calculations and may affect SLA.

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 Calculation setting under the General tab when editing the associated status page:

There are two possible scenarios that can occur when “This Incident’s duration…” option is checked:

  • Scenario 1: Status page uses Check-based: downtime will still be counted
  • Scenario 2: Status page uses Incident-based: downtime will not be counted

Select Status Page: an incident must be associated with a single status page. 

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. This is set to true by default.

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

Incidents can also be created and managed through the REST API. To review the endpoints for incidents, please see our API documentation here: https://uptime.com/api/v1/docs/#/statuspages


 

Incident Status and Status Updates

Return

Use the Update section to select an incident state and provide an optional incident description. Markdown is supported for complex formatting. Use double-spacing to begin a new line. Once your update is entered, click Add to see a preview before the update is posted.

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 set to the Resolved state, use the Reset all affected components to Operational checkbox to restore Operational status to all components affected by the incident.

 

Incident Status Types

Return

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:

Incident Status Meaning
Investigating An event is acknowledged and investigation is underway
Monitoring Engineers have released a fix, and the team is closely monitoring the results
Identified The issue has been identified, and a fix is in progress
Notification Used to issue a general notification that does not impact service
Resolved Continued monitoring has confirmed the fix is successful

 

 

All Incidents Overview

Return

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
Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.