> For the complete documentation index, see [llms.txt](https://docs.zapsign.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zapsign.com.br/zapsign-api/english/incident-alerts.md).

# Incident alerts

We maintain an availability standard of at least 99.9% for our applications, ensuring high reliability for users. \
Visit our status page to check the application's availability and identify any issues that might affect your system's operation.

{% embed url="<https://status.zapsign.com.br/>" %}

Any downtime or incidents are communicated via email to the registered addresses. If you prefer to receive real-time updates on incidents and availability, click "Subscribe to updates" on our status page.\ <br>

<figure><img src="https://github.com/AmandaAmani/documenta-ocurso/blob/main/nova%20tela%20de%20status.gif?raw=true" alt="User subscribing to receive email updates about ZapSign&#x27;s status."><figcaption><p>ZapSign service status page</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zapsign.com.br/zapsign-api/english/incident-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
