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

# Status Pages

This page explains how Status Pages provide real-time updates on 360dialog and Meta platform incidents and maintenance.

Status Pages provide live information about service incidents or outages affecting 360dialog or Meta platforms. Checking these pages first helps identify whether an issue is related to a known incident, avoiding unnecessary investigation.

### 360Dialog Status Page

Managed by 360Dialog. Provides updates on platform availability, API incidents, and maintenance notices.

{% embed url="<https://status.360dialog.com/>" %}

### Meta Status Page

Managed by Meta. Reports incidents affecting Meta platforms (360Dialog has no control over content).

{% embed url="<https://metastatus.com/whatsapp-business-api>" %}

### When to check&#x20;

* Messages are not being sent or received.
* The 360dialog Hub or API is unavailable.
* A platform-level issue is suspected, such as a Meta or WhatsApp Business API incident.

If an incident is already reported, please inform our Support Team that your case is related to that ongoing issue.

### **Incident Notifications**

To receive updates, users must subscribe to the status page. Multiple notification channels are available, including: Email, Slack and Webhooks.

New customer signups are automatically added for email notifications. However, the subscription must be confirmed by the customer before notifications are activated.

{% hint style="info" %}
**Tip**\
Subscribing to both the 360dialog and Meta status pages ensures the most comprehensive set of incident notifications.
{% endhint %}


---

# 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.360dialog.com/docs/support/status-pages.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.