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

# Status Page

Check whether akenza itself is affected before you start debugging.

The status page at [status.akenza.io](https://status.akenza.io/) reports the live state of the akenza platform, so it is the first place to look when something stops working and you want to know whether the cause is on your side.

## What it covers

Each part of the platform is reported separately, which usually tells you straight away how far a problem reaches:

<table><thead><tr><th width="250">Component</th><th>What it covers</th></tr></thead><tbody><tr><td><strong>Frontend</strong></td><td>The akenza application in the browser.</td></tr><tr><td><strong>API</strong></td><td>The <a href="/reference/api-documentation.md">REST API</a>, including everything your own applications call.</td></tr><tr><td><strong>External APIs</strong></td><td>The interfaces akenza exposes to and consumes from third parties.</td></tr><tr><td><strong>Data Gateway</strong>, and separately <strong>HTTP</strong>, <strong>MQTT</strong>, and <strong>CoAP</strong></td><td>Ingestion of device data, split by protocol, so an incident on one does not imply an incident on the others.</td></tr><tr><td><strong>Swisscom CMP LPN</strong> and <strong>Swisscom CMP Mobile</strong></td><td>The connectivity integrations for the Swisscom LPN and mobile networks.</td></tr></tbody></table>

Alongside the current state, the page keeps a history of past incidents with the updates published during each one, and uptime over the last 90 days.

## Subscribing to updates

Subscribe on the status page itself to hear about incidents as they are published rather than noticing them by accident. Notifications are available by **email**, in **Slack**, and as an **RSS or Atom feed**, the last of which is the one to point a monitoring tool at.

{% hint style="info" %}
Worth doing for whoever is on call for your fleet. An incident on a data gateway looks exactly like devices going quiet, and knowing which of the two you are dealing with saves an afternoon.
{% endhint %}

## If your problem is not on the status page

Not every problem is platform-wide, and an incident is only listed once it has been identified. If everything reads operational but something is still wrong for you, raise it:

{% content-ref url="/pages/-MVH9M6FYQlJLyitY0Bo" %}
[Service Desk](/faq/service-desk.md)
{% endcontent-ref %}


---

# 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.akenza.io/faq/status-page.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.