Is Aiven down?

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.

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.

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.

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

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)

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)

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)

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)

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