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.
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".
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.
When creating or updating an incident, you will also give a brief message explaining the current situation.
Note: This field accepts some HTML tags.
We allow you to specify which components are affected by an incident so that your component status and incident updates stay in sync, and your users get a complete picture of service health. If you are on a Business plan or higher and have the component subscriptions feature turned on, your subscribers can fine tune their notifications.
You can toggle whether or not notifications are sent out to your subscribers. You must indicate that one or more components is affected by the incident in order to send notifications at all.
We allow you to sync a Twitter account with Statuspage.io to automatically tweet updates when you create or update an incident.