Aiven Outage History

Aiven is up right now

Aiven had 27 outages in the last 2 years totaling 237h 5m of downtime — averaging 1.1 incidents per month.

There were 27 Aiven outages since July 8, 2025 totaling 237h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.aiven.io

Minor June 16, 2026

Kafka upgrades to 3.9 are paused

Detected by Pingoru
Jun 16, 2026, 11:05 AM UTC
Resolved
Jun 16, 2026, 11:05 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jun 11, 2026, 03:25 PM UTC

    Status: Investigating We have identified an issue affecting KRaft migrations during Kafka upgrades to version 3.9, and have temporarily paused those upgrades while we investigate. If you try to upgrade now, your request will be rejected with an error asking you to contact support. We will re-enable upgrades once the issue is resolved. Impact: Running Kafka services are not affected and continue to operate normally. Customers who attempt to upgrade a Kafka service to version 3.9 or later will receive an HTTP 403 error and the upgrade will not proceed. No data or service availability is impacted.

  2. monitoring Jun 15, 2026, 02:01 PM UTC

    Status: Monitoring We have a fix prepared, which is currently undergoing final verification. If validation is successful, we will proceed with deployment shortly. As a result, the incident is now moving into a monitoring phase while we observe system stability after the changes. We will re-enable Kafka upgrades to version 3.9 once we confirm the issue is fully resolved.

  3. resolved Jun 16, 2026, 11:05 AM UTC

    Status: Resolved The issue has been resolved. All affected functionality is operating normally.

Read the full incident report →

Minor June 9, 2026

Backup and restore failures affecting some Aiven for PostgreSQL services

Detected by Pingoru
Jun 09, 2026, 04:57 PM UTC
Resolved
Jun 09, 2026, 04:57 PM UTC
Duration
—
Affected: Aiven
Timeline · 5 updates
  1. investigating Jun 09, 2026, 03:10 PM UTC

    Status: Investigating Aiven engineers are currently investigating a bug on Aiven for PostgreSQL that causes affected cluster fail to take backups and restore from backup. Known affected clouds are AWS and DigitalOcean. Thank you for your patience as we continue our work on this incident. Affected components Aiven (Partial outage)

  2. identified Jun 09, 2026, 03:57 PM UTC

    Status: Identified Our team has identified a potential root cause and is working to fix the issue on the affected services. Affected components Aiven (Partial outage)

  3. monitoring Jun 09, 2026, 04:18 PM UTC

    Status: Monitoring The fix has been applied to the affected services, and Aiven will continue to monitor to confirm that no further action is needed. Thank you for your patience. Affected components Aiven (Partial outage)

  4. monitoring Jun 09, 2026, 04:36 PM UTC

    Status: Monitoring Correction: Aiven for Apache Kafka services as well as Aiven for PostgreSQL services were affected. All services identified to have the issue have been fixed as per the previous status message. Affected components Aiven (Partial outage)

  5. resolved Jun 09, 2026, 04:57 PM UTC

    Status: Resolved The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved. Affected components Aiven (Operational)

Read the full incident report →

Minor May 25, 2026

Service operations affected in Azure

Detected by Pingoru
May 25, 2026, 03:54 AM UTC
Resolved
May 25, 2026, 03:54 AM UTC
Duration
—
Affected: Aiven
Timeline · 3 updates
  1. investigating May 25, 2026, 02:29 AM UTC

    Status: Investigating We are experiencing an issue affecting service operations across Azure regions. While existing services remain up and running, operations such as service creation, plan changes, and scheduled maintenance are currently failing. We are actively working on a fix to restore full functionality as quickly as possible. We will continue to update here on the progress of this issue. Affected components Aiven (Partial outage)

  2. identified May 25, 2026, 03:48 AM UTC

    Status: Identified We have identified the root cause and are currently deploying a fix to resolve the issues affecting service operations across Azure regions. While existing services remain up and running, operations such as service creation, plan changes, and maintenance updates are currently failing. We are monitoring the deployment closely to ensure full functionality is restored as quickly as possible. We will continue to update here on the progress of this issue. Affected components Aiven (Partial outage)

  3. resolved May 25, 2026, 03:54 AM UTC

    Status: Resolved We have resolved the underlying cause of the issue affection service operations in our Azure regions. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one. Affected components Aiven (Operational)

Read the full incident report →

Minor May 20, 2026

Issue affecting services in DigitalOcean NYC3 region

Detected by Pingoru
May 20, 2026, 02:38 AM UTC
Resolved
May 20, 2026, 02:38 AM UTC
Duration
—
Affected: Aiven
Timeline · 2 updates
  1. investigating May 20, 2026, 01:15 AM UTC

    Status: Investigating We are experiencing performance degradation and node unresponsiveness affecting some Aiven services hosted in the DigitalOcean NYC3 region. This is tied to an underlying infrastructure issue currently being tracked by our cloud provider. You can monitor their infrastructure health directly on the DigitalOcean Status Page: https://status.digitalocean.com/incidents/spgd2scvttth Our engineering team is actively investigating the extent of the impact on our services and working to mitigate issues where possible. Affected components Aiven (Degraded performance)

  2. resolved May 20, 2026, 02:38 AM UTC

    Status: Resolved This issue is now resolved. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue. Affected components Aiven (Operational)

Read the full incident report →

Minor May 15, 2026

Multiple Aiven for Apache Kafka services experiencing disruption

Detected by Pingoru
May 15, 2026, 11:13 PM UTC
Resolved
May 15, 2026, 11:13 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating May 14, 2026, 06:55 AM UTC

    Status: Investigating We are currently aware of an issue affecting Aiven for Kafka services. Our teams are currently investigating the root cause as a priority. We will continue to provide status updates as they become available.

  2. identified May 14, 2026, 07:36 AM UTC

    Status: Identified We have identified the root cause of the issue affecting multiple Aiven for Apache Kafka services and are currently working to restore the affected services. Our teams are actively applying fixes and will continue to provide updates as progress is made.

  3. monitoring May 14, 2026, 10:49 AM UTC

    Status: Monitoring We have applied a fix to the affected services and are seeing recovery progress. Our team is closely monitoring the platform and will continue to mitigate any remaining impact if needed.

  4. monitoring May 14, 2026, 03:13 PM UTC

    Status: Monitoring Our team has seen the impacted services recover, and we are now closely monitoring for any remaining impact.

  5. resolved May 15, 2026, 11:13 PM UTC

    Status: Resolved We have resolved the underlying cause of the kafka service disruption. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.

Read the full incident report →