> 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-update-an-incident.md).

# How to Update an Incident

#### Steps to Update an Incident:

1. Open **Incidents** in the sidebar and click the incident you want to update (**"Edit"** button)
2. Click **➕ Add Update or Mark as Resolved** in the incident timeline.

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

3. **Resolution Stage** – pick the current phase.
4. **Update Description** – enter a concise message (supports Markdown). Examples:

*“We’ve rolled back the faulty release; monitoring recovery.”*

5. *(Optional)* Adjust **Severity** if impact has changed.
6. Hit **Update Incident** to conclude this step.

<figure><img src="/files/3GjHcmTQlFtffmoFGZ1z" alt=""><figcaption></figcaption></figure>

Choose **Resolved** only when:

* All user impact has stopped.
* Fix is deployed and verified.
* You’re ready to close subscriber alerts.

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

A “**resolved**” update automatically sets the service status back to **OK**.

Need assistance? Contact us via chat or email us at **<support@isdown.app>.**

***

Related Articles

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


---

# 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, and the optional `goal` query parameter:

```
GET https://help.isdown.app/custom-monitor/how-to-update-an-incident.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.