Status Page

Check whether akenza itself is affected before you start debugging.

The status page at 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:

Component	What it covers
Frontend	The akenza application in the browser.
API	The REST API, including everything your own applications call.
External APIs	The interfaces akenza exposes to and consumes from third parties.
Data Gateway, and separately HTTP, MQTT, and CoAP	Ingestion of device data, split by protocol, so an incident on one does not imply an incident on the others.
Swisscom CMP LPN and Swisscom CMP Mobile	The connectivity integrations for the Swisscom LPN and mobile networks.

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.

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.

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:

Service Desk