> For the complete documentation index, see [llms.txt](https://help.isdown.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.isdown.app/custom-monitor/how-to-add-an-incident.md).

# How to Add an Incident

#### Before You Start

* Only **Custom Services** can be selected in the *Affected Service* field (3rd-party services are reported automatically by IsDown).

#### Steps to add an Incident

1. In the sidebar, click **Incidents → New Incident**.

<figure><img src="/files/SRc2RnDfyecAbNrcIbPY" alt=""><figcaption></figcaption></figure>

2. **Title** – Enter a short, clear summary (Example: “Checkout API latency”).
3. **Affected Service** – Pick the custom service that’s impacted.
4. **Severity** – Select **Minor** (partial disruption) or **Major** (widespread/critical).
5. **Updates** panel:
   * Choose the initial **Resolution Stage** (defaults to **Investigating**).
   * Type your first **Update Description** (what you know so far).
6. Click **Create Incident**. Notifications are sent instantly to all configured channels.

<figure><img src="/files/mtjuQ04tnvwDxbgu5b2K" alt=""><figcaption></figcaption></figure>

If you need any assistance, please contact us via chat or email us at **<support@isdown.app>.**

***

**Related Articles**

* [**How to make an Update from an Incident**](https://help.isdown.app/how-to-make-an-update-from-an-incident)
* [**How to Delete a Custom Service**](https://help.isdown.app/how-to-delete-custom-service)
* [**How to Create Custom Services**](https://help.isdown.app/custom-monitor/how-to-create-custom-services)