> For the complete documentation index, see [llms.txt](https://docs.complycube.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.complycube.com/documentation/trust-and-compliance/service-status.md).

# Service Status

Monitor ComplyCube service status, uptime, incidents, and scheduled maintenance updates in real time.

### Overview

Use the ComplyCube status page to monitor real-time service status, uptime, incidents, and maintenance updates.

{% hint style="success" %}
ComplyCube has maintained **100% uptime** across all regions for the past 5 years.
{% endhint %}

{% hint style="info" %}
View live status, incident history, and maintenance notices on the [ComplyCube Status Page](https://status.complycube.com).
{% endhint %}

### Platform status and uptime

The status page helps you track:

* Current platform and service availability.
* Incident updates and resolution progress.
* Scheduled maintenance notices.

### Incident updates

When a service issue affects availability or performance, updates are posted on the status page as the incident progresses.

Published updates may include:

* Incident identification and affected services.
* Ongoing status updates.
* Resolution confirmation and follow-up details.

### Scheduled maintenance notices

Planned maintenance is announced on the status page in advance whenever possible.

Maintenance notices help you prepare for:

* Expected service impact.
* Planned maintenance windows.
* Completion updates after work finishes.

### Support and escalation

If you see an issue that is not reflected on the status page, contact your usual ComplyCube support channel or account manager.


---

# 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.complycube.com/documentation/trust-and-compliance/service-status.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.