Is Aiven down?

Status: Investigating We are currently experiencing delays in the creation of new virtual machines, which may affect the provisioning of new services and nodes. An ongoing incident with an upstream cloud provider (DigitalOcean) is preventing new VM creation in all DigitalOcean regions. Additionally, we are observing delays in new VM creation across all other cloud providers. Impact: DigitalOcean: New VM creation is currently unavailable in all DO regions. All other clouds: New VM creation may be delayed longer than usual. Existing services are not affected and continue to run normally. This issue impacts only the creation of new VMs (e.g., new service provisioning, node replacements, and scaling operations that require new VMs). Our engineering team is actively monitoring the situation and working to reduce the provisioning backlog. We are tracking the upstream provider's recovery and will restore normal provisioning times as soon as possible. We apologize for the inconvenience caused by this issue. Affected components Aiven (Degraded performance)

Status: Investigating New VM creation across most cloud providers is now recovering, and provisioning times are slowly returning to normal. Services that were previously delayed should now be creating successfully soon. Current status • All clouds except DigitalOcean: New VM creations are slowly returning to normal pace. We are continuing to monitor to confirm provisioning times remain stable. • DigitalOcean: New VM creation remains unavailable in DigitalOcean regions due to the ongoing upstream provider incident. We are tracking the provider's recovery and will restore normal provisioning as soon as it is resolved. Our engineering team is actively monitoring provisioning performance across all clouds and continues to track the DigitalOcean provider's recovery. Thank you for your patience. Affected components Aiven (Degraded performance)

Status: Resolved New VM creation has returned to normal across all cloud providers, including DigitalOcean. * VM provisioning is operating normally across all regions. * The upstream DigitalOcean incident has been resolved. * We are continuing to monitor the infrastructure to ensure stable provisioning. The incident is now resolved. Thank you for your patience. Affected components Aiven (Operational)

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)

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

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)

Status: Investigating We are currently investigating an issue affecting services running on DigitalOcean that is causing delays in node lifecycle management. As a result, any operations on DigitalOcean-hosted services that require creating, deleting, or replacing nodes will experience delays. Impacted operations (on DigitalOcean only) include: • Creating new services • Deleting existing services • Powering services up or down • Scheduled maintenance updates • Service scaling and plan upgrades Note: Existing, running services on DigitalOcean are currently unaffected and operating normally. Services running on other cloud providers (AWS, GCP, Azure, UpCloud) are completely unaffected. Our engineering team is actively working to resolve the issue, and we will provide further updates as soon as more information is available. We apologize for the inconvenience. Affected components Aiven (Partial outage)

Status: Investigating We have identified that the previously reported issue affecting node lifecycle management is not isolated to a single cloud provider, but is currently affecting services across all cloud providers. As a result, any operations that require creating, or replacing nodes will experience significant delays regardless of the underlying cloud hosting platform. We have stopped all pending maintenance updates to help mitigate the impact. Impacted operations across all providers include: - Creating new services - Powering services up - Scheduled maintenance updates - Service scaling and plan upgrades Note: Aiven for MySQL services are completely unaffected by this issue. For all other service types, existing, running services remain unaffected and continue to operate normally. Our engineering teams are actively working to resolve the root cause across our infrastructure, and we will provide further updates as the situation develops. We apologize for the continued inconvenience. Affected components Aiven (Partial outage)

Status: Monitoring We have implemented a mitigation for the infrastructure issue affecting node lifecycle management, and we are now seeing service operations return to normal. We are closely monitoring the platform to ensure stability. Pending operations such as service creations, deletions, and maintenance updates are beginning to process, though it may take some time to clear the remaining backlog. Affected components Aiven (Partial outage)

Status: Resolved We have resolved the underlying cause of this issue. 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)

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.

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.

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.

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.

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.

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.

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.

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.