Is akenza down?
Last checked 6m agoNo incidents right now.
akenza is operational right now. Last checked 6m ago; the most recent incident resolved 6d ago.
Real-time akenza status, recent outages, and incident history — pulled directly from akenza's official status page at https://status.akenza.io every 5 minutes. Pingoru tracks 7 akenza services and has captured 15 incidents in the last 90 days (99.20% uptime). Get email, Slack, Discord, or webhook alerts the moment akenza reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- HTTP Data GatewayMQTT Data GatewayCoAP Data Gateway
Timeline · 3 updates
- investigating · Sep 10, 2026, 07:52 AM UTC
We are currently investigating this issue.
- monitoring · Sep 10, 2026, 08:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Sep 10, 2026, 10:40 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- API
Timeline · 4 updates
- investigating · Sep 09, 2026, 05:26 PM UTC
We are currently investigating this issue.
- identified · Sep 09, 2026, 08:18 PM UTC
The issue has been identified. We are still seeing an increased data processing lag for akenza DB outputs and are working on a fix.
- monitoring · Sep 09, 2026, 11:04 PM UTC
A fix has been implemented and we are monitoring as the processing lag is gradually being caught up for some remaining devices.
- resolved · Sep 10, 2026, 05:06 AM UTC
All lags are caught up and this incident has been resolved.
Latest: All lags are caught up and this incident has been resolved.
-
- API
Timeline · 3 updates
- investigating · Aug 27, 2026, 04:34 PM UTC
We are currently investigating this issue.
- monitoring · Aug 27, 2026, 04:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Aug 27, 2026, 07:14 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Aug 19, 2026, 05:38 AM UTC
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.
Latest: 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.
-
-
Timeline · 1 update
- resolved · Jul 22, 2026, 09:54 PM UTC
Due to a configuration error, the websocket API for subscribing to live data streams was not available between 06:00PM and 11.55PM.
Latest: Due to a configuration error, the websocket API for subscribing to live data streams was not available between 06:00PM and 11.55PM.
-
See the full akenza outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse akenza outage history →Or sign up free to get alerts when akenza breaks · 10 free monitors · No credit card
- Started Sep 10, 2026, 07:52 AM UTC · Resolved Sep 10, 2026, 10:40 AM UTC · 2h 48m
- Started Sep 09, 2026, 05:26 PM UTC · Resolved Sep 10, 2026, 12:30 AM UTC · 7h 4m
- Started Aug 27, 2026, 03:55 PM UTC · Resolved Aug 27, 2026, 07:14 PM UTC · 3h 18m
- Started Aug 19, 2026, 05:38 AM UTC · Resolved Aug 19, 2026, 04:30 AM UTC · —
- Started Jul 22, 2026, 09:54 PM UTC · Resolved Jul 22, 2026, 04:00 PM UTC · —
- Started Jun 22, 2026, 06:53 AM UTC · Resolved Jun 21, 2026, 11:30 PM UTC · —