# Incidents on status page

#### Step 1: Create new incident

On the [Status Page dashboard](https://statuspage.spike.sh), click on 'Incidents' in the left sidebar. Then click on 'New incident' button on the Incidents page.

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-a53b839bf94d781dfe054f7bab503ec1921d0928%2Fcreate%20incident%202.png?alt=media\&token=53ffe272-ded4-4bb4-a858-1c48d8525969)

In the 'Create incident' form, add details about your incident. Add a **title** and a **description** to describe the tech issue.

Select the **affected components** - these are system components that are impacted by the incident. For example, if it is a problem with mobile app only, choose that from the component list. Then select the current state for that component. Here is what the different component states mean -

* **Operational** - This component is functioning correctly.
* **Degraded performance** - The component is functioning, but at a less than optimal performance e.g. longer response times with APIs.
* **Partial outage** - This component is not working for some users and/or in some situations.
* **Critical outage** - This component is not functioning correctly for a majority of the users.
* **Planned maintenance** - This state is used when you have scheduled maintenance activity on some components. You can create a Planned Maintenance event in such cases.

You can specify the **date and time** at which the incident was identified. This will also be used to calculate the outage time for your components.

You can choose the **Incident impact** value based on your assessment of the situation. You can change this as you get more information about the incident.

Finally, you can choose whether to **notify your status page subscribers** via email about this incident. If you select this option, an email will be sent to all subscribers of the status page.

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-ca65b9f608d86401e0a8030d47bd17e14e62103a%2Fcreate%20incident%203.png?alt=media\&token=76920152-ffd9-4f84-98e1-a4ccb59b82d4)

You should

#### Step 2: Add updates to an incident

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-808b1d0c0e45ae75b407c9f84068cabea41f353c%2Fcreate%20incident%204.png?alt=media\&token=2ba570d4-3f14-43b4-bfd9-efec16e250e6)

As you get more information about the incident, you can **add updates** to the incident. Click on 'Add status update' on the incident page in your dashboard.

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-8ec4fdb3551b3cc09109704501eba4f49b850f6c%2Fcreate%20incident%205.png?alt=media\&token=6e0eab5c-0257-463d-9fcd-b5aa4b857e92)

For each update, you can choose the current Incident status. This can be one of -

* **Investigating** - You are looking into the issue.
* **Identified** - You have identified the cause of the issue and/or the fix to solve it.
* **Resolved** - You have fixed the problem and will most likely move the affected components back to Operational state.
* **Postmortem** - This update is after the issue is resolved and meant to communicate your findings and steps you will take to prevent the issue in the future.
* **Update** - This is a generic update to the incident that can be used when any of the above statuses don't apply.

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-6564af402cf3706cc947c77b4a27e7b432f9dac2%2Fcreate%20incident%206.png?alt=media\&token=ee47a993-dac0-440e-a380-e3309b143384)

You can see the incident updates on your public status page.