pingoru pingoru akenza had 43 outages in the last 2 years totaling 58h 21m of downtime, averaging 1.8 incidents per month.
There were 43 akenza outages since May 16, 2025 totaling 58h 21m of downtime. Each is summarised below. Incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating an issue with Azure Open AI services that leads to increased errors with Genio related features.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 6.42AM and 6.46AM we observed an increased error rate for MQTT uplinks during which messages with QoS < 2 might not have been processed.
Due to a configuration error, the websocket API for subscribing to live data streams was not available between 06:00PM and 11.55PM.
Between 1.30 and 2.15AM, we have experienced increased data processing lags for akenza DB outputs.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.
Between 02.10AM and 03.00AM we experienced increased API errors and data processing delays for some endpoints.
Swisscom CMP LPN devices currently cannot be edited, registered or de-registered.
This incident has been resolved.
Between 10.55 and 11.05 we experienced increased errors and timeouts when loading the asset inventory.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have observed increased API and slightly increased processing error rates between 00.35AM and 01.10AM CEST.
On Wednesday 15th April 2026 between 14h and 19h (Zurich Time, UTC+2), some hourly aggregation data were not computed by the system. A fix was deployed on 19h and the following hourly aggregation data were all correctly computed.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and data is no longer processed with increased latency. We are currently monitoring the results.
This incident has been resolved.
We are currently investigating an issue with data processing logs where some of the debugging logs are not up to date.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
During a short time frame (10.12-10.14AM), we experienced an increased amount of 404 errors when authenticating with api keys.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Ingestion of aggregate data is now running on time again. Delays have been catched up. Monitoring the fix in progress.
This incident has been resolved.
We are currently investigating this issue.
The problem has been identified, most of the delays have been caught up, however some delays still require reprocessing.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.