Overview

Incidents are the main way to communicate with your customers when you are having downtime. During a downtime-related event, you can add an incident to your page describing the issue, what you're doing about it, and when you expect the issue to be fixed. The incident will be posted to your status page so your customers can stay up-to-date with any problems that may be affecting them.

As time goes on and the cause of the incident is identified and then later fixed, you can add updates to incidents to reflect the current status.

Primary Fields

Name

Incidents are given a name that is representative of the issue as-a-whole that's being talked about. Examples are things like "DB Connectivity Issues", "API Requests Timing Out", and "DNS Issues".

Incident Status

Incidents have one of four distinct statuses. When creating or updating an incident you will specify which of the states the incident is currently in.

  • Investigating - you are seeing the symptoms of an issue but are unaware what the root cause.
  • Identified - you have found the root cause of the incident and are working on a fix.
  • Monitoring - you believe you have successfully fixed the issue and are waiting for the symptoms to subside.
  • Resolved - the root cause of the issue has been eliminated and your systems are back to 100% performance.
Message

When creating or updating an incident, you will also give a brief message explaining the current situation.

Note: This field accepts HTML.

Secondary Fields

Tweet Update

We allow you to sync a Twitter account with StatusPage.io to automatically tweet updates when you create or update an incident.

Components Affected

We allow you to specify which components are affected by an incident so that your customers can subscribe to get notifications when specific components are affected. This feature is only available when component subscriptions is turned on and for accounts on the Business plan.