> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/troubleshooting/common-issues/status-page-notifications.md).

# How to receive updates from Digibee Status Page

Learn how to receive information from the Digibee Integration Platform status page.

You can receive notifications from our Status Page whenever Digibee announces, updates, or resolves an incident. Simply choose your preferred communication method and subscribe. Follow the steps below:

1. Access the [Digibee Status Page](https://status.godigibee.io/).
2. Click the **Subscribe to Updates** button in the top right corner.
3. Use the icons at the top of the pop-up to select your preferred communication method. The options are: 

* Email
* Slack notification
* RSS Feed or Atom Feed

4. Input your data according to the chosen method and click the **Subscribe** button to confirm. 


---

# 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.digibee.com/documentation/troubleshooting/common-issues/status-page-notifications.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.