> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/status-pages/create-public-incident-on-status-page.md).

# Incidents on status page

Use the status page dashboard to create public incidents and keep customers informed as the situation develops.

## Create a new incident

On the [Status Page dashboard](https://statuspage.spike.sh), click **Incidents** in the left sidebar, then click **New incident**.

<figure><img src="/files/g8nBNsSnw1xv6yFue80l" alt="Create a new incident on Spike status page"><figcaption></figcaption></figure>

Fill in the **title** and **description** to describe the issue.

Select the **affected components**: the parts of your system impacted by the incident.

For each component, set its current state:

* **Operational**: The component is functioning correctly.
* **Degraded performance**: The component is working but below normal performance, such as slower API response times.
* **Partial outage**: The component is not working for some users or in some situations.
* **Critical outage**: The component is not functioning for most users.
* **Planned maintenance**: The component has scheduled maintenance. Consider creating a [Planned Maintenance event](/status-pages/create-planned-maintenance-on-status-page.md) instead.

Set the **date and time** the incident was identified. Spike uses this to calculate outage duration for affected components.

Set the **incident impact** based on your assessment. You can update this as the situation develops.

To **notify subscribers** by email, check the notification option. Spike sends an email to all status page subscribers.

<figure><img src="/files/WSGNeNyS7ZqZi06BeyOs" alt="Incident creation form on Spike status page"><figcaption></figcaption></figure>

## Add updates to an incident

<figure><img src="/files/iSuyXHyhNvkEOy1MB51w" alt="Incident page in Spike status page dashboard"><figcaption></figcaption></figure>

As you learn more, post updates to keep subscribers informed. Click **Add status update** on the incident page.

<figure><img src="/files/sI33tjF4aKVQjsaOvcKN" alt="Add a status update to an incident on Spike"><figcaption></figcaption></figure>

For each update, select the current incident status:

* **Investigating**: You are looking into the issue.
* **Identified**: You have identified the cause or the fix.
* **Resolved**: The issue is fixed. Move affected components back to Operational.
* **Postmortem**: The issue is resolved. Use this to share findings and steps to prevent recurrence.
* **Update**: A general update when none of the above statuses apply.

<figure><img src="/files/5Koaz6WHwZ0ML7iXmheF" alt="Incident status updates visible on public status page"><figcaption></figcaption></figure>

Updates appear on your public status page immediately after posting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spike.sh/status-pages/create-public-incident-on-status-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.