Aiven Outage History

Aiven is up right now

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

There were 27 Aiven outages since October 17, 2025 totaling 182h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.aiven.io

Minor September 30, 2026

Creation of new service nodes disrupted

Detected by Pingoru
Sep 30, 2026, 06:35 AM UTC
Resolved
Sep 30, 2026, 06:35 AM UTC
Duration
—
Affected: Aiven
Timeline · 4 updates
  1. investigating Sep 16, 2026, 12:21 PM UTC

    Status: Investigating We are investigating issues with creating new nodes for services on the Aiven platform currently. The effect is slower creation time for new nodes. Any any event where a new node is created are impacted such as failovers, switchovers, upgrades and maintenance updates. Our engineers are currently investigating the root cause and working on a fix for the issue. We apologise for the inconvenience caused by this issue. We will provide a further update as our team continues on the solution for this situation. Affected components Aiven (Degraded performance)

  2. monitoring Sep 16, 2026, 01:58 PM UTC

    Status: Monitoring We are monitoring our mitigating actions to issues with creating new nodes for services on the Aiven platform. Our engineers have done mitigating steps and we see improvements in the node creation, but we'll continue investigating and monitoring of the issue. We apologise for the inconvenience caused by this issue. We will provide a further update as our team continues monitoring and triaging this situation. Affected components Aiven (Degraded performance)

  3. monitoring Sep 16, 2026, 03:04 PM UTC

    Status: Monitoring We have completed our mitigating actions and the creation of new nodes for services on the Aiven platform has returned to normal. Customers can now proceed with any operations that were delayed during this issue, including service creation, scaling, upgrades, maintenance updates and configuration changes. Operations that were left pending should continue automatically. Our engineers continue to monitor the platform to confirm the issue is fully resolved. We apologise for the inconvenience caused by this issue. We will provide a further update as our team completes monitoring of this situation. Affected components Aiven (Degraded performance)

  4. resolved Sep 30, 2026, 06:35 AM UTC

    Status: Resolved We have resolved the underlying cause of the new node creation and new nodes are able to be created without issues. 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 September 30, 2026

Issue with PostgreSQL major version upgrade

Detected by Pingoru
Sep 30, 2026, 12:41 AM UTC
Resolved
Sep 30, 2026, 12:41 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Sep 29, 2026, 08:14 PM UTC

    Status: Investigating We are currently investigating an issue affecting Aiven for PostgreSQL services, where a major version upgrade can leave the service in an unusable state. We advise customers not to initiate a PostgreSQL major version upgrade at this time. If you have already started a major version upgrade and your service is not responding, please contact our support team at [email protected]. Our engineering teams are actively working to identify the root cause and restore affected services. We will provide further updates as soon as more information is available. We apologize for the inconvenience.

  2. identified Sep 29, 2026, 09:59 PM UTC

    Status: Identified We have a mitigation that we are rolling out for the issue affecting Major version upgrade on Aiven for PostgreSQL services. Please continue to refrain from triggering major version upgrades for the moment. Affected services are being restored as the mitigation is deployed. We will provide further updates as the rollout progresses. We apologize for the inconvenience.

  3. identified Sep 29, 2026, 11:50 PM UTC

    Status: Identified PostgreSQL major version upgrades can be performed again. A small number of services affected by an earlier failed upgrade are now being repaired. We will contact customers directly if any action is needed on their side, and we'll post another update here once the repairs are complete.

  4. monitoring Sep 30, 2026, 12:30 AM UTC

    Status: Monitoring All customer services affected by this issue have been restored, and no further action is needed on your side. It is now safe to proceed with PostgreSQL major version upgrades. We apologise for the disruption this caused.

  5. resolved Sep 30, 2026, 12:41 AM UTC

    Status: Resolved All customer services affected by this issue have been restored, and no further action is needed on your side. It is now safe to proceed with PostgreSQL major version upgrades. We apologise for the disruption this caused.

Read the full incident report →

Minor September 21, 2026

Aiven Console is down

Detected by Pingoru
Sep 21, 2026, 08:25 AM UTC
Resolved
Sep 21, 2026, 08:25 AM UTC
Duration
—
Affected: Aiven
Timeline · 4 updates
  1. investigating Sep 21, 2026, 04:57 AM UTC

    Status: Investigating We are currently investigating reports of users being unable to log in to the Aiven console. We will share further updates as soon as possible. Affected components Aiven (Partial outage)

  2. investigating Sep 21, 2026, 05:27 AM UTC

    Status: Investigating We are still investigating an issue affecting the Aiven Console. Customers are currently unable to create or submit new support tickets directly through the portal. If you require assistance with an urgent issue unrelated to the Aiven Console being down, please send an email to [email protected]: mailto:[email protected]. Our support team will process your request directly. Affected components Aiven (Partial outage)

  3. monitoring Sep 21, 2026, 06:01 AM UTC

    Status: Monitoring A fix has been deployed for Aiven Console and portal functionality is restored. We are currently monitoring performance. If you encounter any issues, please email [email protected]: mailto:[email protected] Affected components Aiven (Partial outage)

  4. resolved Sep 21, 2026, 08:25 AM UTC

    Status: Resolved This incident has been resolved. Aiven Console login and support ticket creation through the portal are fully functional again. We continued to monitor performance and have seen no further issues. If you encounter any problems, please email [email protected]: mailto:[email protected]. Affected components Aiven (Operational)

Read the full incident report →

Minor July 29, 2026

Aiven Dynamic Disk Sizing (DDS) failures

Detected by Pingoru
Jul 29, 2026, 05:07 PM UTC
Resolved
Jul 29, 2026, 05:07 PM UTC
Duration
—
Affected: Aiven
Timeline · 3 updates
  1. investigating Jul 29, 2026, 02:29 PM UTC

    Status: Investigating We are investigating an issue affecting Dynamic Disk Sizing (DDS), where resize operations may fail for a small subset of newly created nodes. Mitigations are currently underway. Affected components Aiven (Partial outage)

  2. identified Jul 29, 2026, 03:17 PM UTC

    Status: Identified Issue has been identified and fixes are being applied. Thank you for your patience. Affected components Aiven (Partial outage)

  3. resolved Jul 29, 2026, 05:07 PM UTC

    Status: Resolved Our team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences. Affected components Aiven (Operational)

Read the full incident report →

Minor June 25, 2026

Terraform & Kubernetes operators - List Databases API Error (400)

Detected by Pingoru
Jun 25, 2026, 01:14 PM UTC
Resolved
Jun 25, 2026, 01:14 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Jun 25, 2026, 10:16 AM UTC

    Status: Identified We are currently investigating an issue affecting Terraform & Kubernetes operator users receiving 400 errors when using aiven_pg_database. This is impacting aiven_pg_database and potentially other service types. The root cause has been identified and a fix is in progress. We will provide an ETA as soon as it is available.

  2. monitoring Jun 25, 2026, 12:27 PM UTC

    Status: Monitoring A fix has been applied and the issue is expected to be resolved. We are continuing to monitor closely as we work to restore full system operation. We apologise for the inconvenience caused by this issue.

  3. resolved Jun 25, 2026, 01:14 PM UTC

    Status: Resolved The issue has been resolved. Terraform & Kubernetes operator users should no longer experience 400 errors when using aiven_pg_database. We apologize for any inconvenience caused.

Read the full incident report →

Minor June 25, 2026

Kafka upgrade to 3.9 paused

Detected by Pingoru
Jun 25, 2026, 11:38 AM UTC
Resolved
Jun 25, 2026, 11:38 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Jun 23, 2026, 02:18 PM UTC

    Status: Investigating We have paused Kafka 3.8 ->3.9 upgrades as we are investigating an issue with KRaft migration during the upgrade. Aiven is actively monitoring affected services and applying mitigations where required. Impact: Existing Kafka services continue to run. Customers attempting to upgrade Kafka services from version 3.8 to 3.9 will not be able to complete the upgrade while KRaft migrations are paused. Next update: We will provide an update once more information is available.

  2. identified Jun 23, 2026, 03:10 PM UTC

    Status: Identified We have identified two separate problems: • An issue in migration code • An upstream bug: https://github.com/apache/kafka/pull/19854 We are working on the fix for the migration issue and back-porting the fix for the upstream bug.

  3. identified Jun 24, 2026, 03:01 PM UTC

    Status: Identified We have identified issues affecting KRaft migrations (Kafka 3.8 to 3.9 upgrades). We have paused all migrations while we work on a fix. If you are experiencing any issues, please contact support.

  4. monitoring Jun 25, 2026, 08:06 AM UTC

    Status: Monitoring We have deployed fixes for the issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades, and migrations have been re-enabled. We are continuing to monitor the situation to ensure services remain stable. If you are experiencing any issues, please contact support.

  5. resolved Jun 25, 2026, 11:38 AM UTC

    Status: Resolved The issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades have been resolved. Fixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring. If you are experiencing any issues, please contact support.

Read the full incident report →

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 →