akenza Outage History

akenza is up right now

There were 13 akenza outages since February 10, 2026 totaling 30h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.akenza.io

Major April 20, 2026

Incident with asset related operations

Detected by Pingoru
Apr 20, 2026, 12:51 PM UTC
Resolved
Apr 20, 2026, 04:24 PM UTC
Duration
3h 33m
Affected: APIFrontend
Timeline · 5 updates
  1. investigating Apr 20, 2026, 12:51 PM UTC

    We are currently investigating this issue.

  2. identified Apr 20, 2026, 01:23 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 20, 2026, 01:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Apr 20, 2026, 02:44 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 20, 2026, 04:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 18, 2026

Increased API error rates

Detected by Pingoru
Apr 18, 2026, 05:27 AM UTC
Resolved
Apr 17, 2026, 10:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 18, 2026, 05:27 AM UTC

    We have observed increased API and slightly increased processing error rates between 00.35AM and 01.10AM CEST.

Read the full incident report →

Notice April 16, 2026

Hourly aggregation data quality incident

Detected by Pingoru
Apr 16, 2026, 10:46 AM UTC
Resolved
Apr 16, 2026, 10:46 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 16, 2026, 10:46 AM UTC

    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.

Read the full incident report →

Minor April 1, 2026

Increased API errors when loading the device inventory

Detected by Pingoru
Apr 01, 2026, 12:29 PM UTC
Resolved
Apr 01, 2026, 01:08 PM UTC
Duration
39m
Affected: API
Timeline · 3 updates
  1. investigating Apr 01, 2026, 12:29 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 01, 2026, 12:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 01, 2026, 01:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 20, 2026

Increased data processing latency

Detected by Pingoru
Mar 20, 2026, 10:29 AM UTC
Resolved
Mar 20, 2026, 01:34 PM UTC
Duration
3h 4m
Affected: HTTP Data GatewayMQTT Data GatewayCoAP Data Gateway
Timeline · 3 updates
  1. investigating Mar 20, 2026, 10:29 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 20, 2026, 10:51 AM UTC

    A fix has been implemented and data is no longer processed with increased latency. We are currently monitoring the results.

  3. resolved Mar 20, 2026, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026

Data processing logs currently not up to date

Detected by Pingoru
Mar 19, 2026, 09:28 AM UTC
Resolved
Mar 19, 2026, 09:41 PM UTC
Duration
12h 13m
Affected: HTTP Data GatewayMQTT Data GatewayCoAP Data Gateway
Timeline · 3 updates
  1. investigating Mar 19, 2026, 09:28 AM UTC

    We are currently investigating an issue with data processing logs where some of the debugging logs are not up to date.

  2. monitoring Mar 19, 2026, 03:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 19, 2026, 09:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Increased message processing latency for akenza database outputs

Detected by Pingoru
Mar 18, 2026, 03:42 PM UTC
Resolved
Mar 18, 2026, 06:54 PM UTC
Duration
3h 12m
Affected: HTTP Data GatewayMQTT Data GatewayCoAP Data Gateway
Timeline · 3 updates
  1. investigating Mar 18, 2026, 03:42 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 18, 2026, 04:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 18, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 14, 2026

Increased error rate for api keys

Detected by Pingoru
Mar 14, 2026, 09:22 AM UTC
Resolved
Mar 14, 2026, 09:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 14, 2026, 09:22 AM UTC

    During a short time frame (10.12-10.14AM), we experienced an increased amount of 404 errors when authenticating with api keys.

Read the full incident report →

Major February 16, 2026

Increased error rate for some query endpoints

Detected by Pingoru
Feb 16, 2026, 03:00 PM UTC
Resolved
Feb 16, 2026, 06:45 PM UTC
Duration
3h 44m
Affected: API
Timeline · 3 updates
  1. investigating Feb 16, 2026, 03:00 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 16, 2026, 03:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 16, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 12, 2026

Delay in ingestion of aggregate data

Detected by Pingoru
Feb 12, 2026, 03:38 PM UTC
Resolved
Feb 12, 2026, 04:39 PM UTC
Duration
1h 1m
Affected: API
Timeline · 3 updates
  1. investigating Feb 12, 2026, 03:38 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 12, 2026, 03:57 PM UTC

    Ingestion of aggregate data is now running on time again. Delays have been catched up. Monitoring the fix in progress.

  3. resolved Feb 12, 2026, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 10, 2026

Increased Processing Latency

Detected by Pingoru
Feb 10, 2026, 11:28 AM UTC
Resolved
Feb 10, 2026, 01:30 PM UTC
Duration
2h 1m
Affected: HTTP Data GatewayMQTT Data GatewayCoAP Data Gateway
Timeline · 3 updates
  1. investigating Feb 10, 2026, 11:28 AM UTC

    We are currently investigating this issue.

  2. identified Feb 10, 2026, 12:24 PM UTC

    The problem has been identified, most of the delays have been caught up, however some delays still require reprocessing.

  3. resolved Feb 10, 2026, 01:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track akenza downtime and outages?

Pingoru polls akenza's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when akenza reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track akenza alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring akenza for free

5 free monitors · No credit card required