Is Aiven Down?

This incident has been resolved. A power outage in Google Cloud's europe-west2-b zone disrupted services running in the europe-west2 region. Nodes in the affected zone were rebooted when the zone recovered. Some affected Aiven for Apache Kafka, Aiven for OpenSearch, Aiven for PostgreSQL and Aiven for Valkey services needed extra recovery steps or node replacement before they returned to normal operation. All affected services have now been restored. We apologise for the disruption. --- [2026-10-20T18:55:19Z] (monitoring) All Aiven services known to be affected by the Google Cloud incident in europe-west2 have been recovered. After Google mitigated the power outage in the europe-west2-b zone, we restored the affected Aiven for Apache Kafka, Aiven for OpenSearch and Aiven for PostgreSQL services by recovering nodes or replacing them. We are continuing to monitor all services in the region to confirm they remain healthy. If you are still experiencing issues with a service in europe-west2, please contact Aiven Support. --- [2026-10-20T18:10:10Z] (monitoring) All PG and Kafka services known to be affected by the Google Cloud incident in europe-west2 have been recovered. We are currently recovering and fixing known Opensearch services. We are continuing to monitor all services in the region to confirm they remain healthy. If you are still experiencing issues with a service in europe-west2, please contact Aiven Support. --- [2026-10-20T14:10:38Z] (investigating) We are continuing to respond to the Google Cloud incident affecting the europe-west2 region. The underlying Google Cloud issue — a power outage in the europe-west2-b zone has been mitigated by Google, and recovery of most workloads has been in progress since 15:10 EEST. Services running in the affected region may be unavailable or degraded while recovery is in progress. We are seeing the recovery of services and are prioritizing the recovery of existing workloads. Customers may not be able to yet create new workloads. We are actively recovering the affected services, including recycling affected Kafka nodes and working through the OpenSearch and PostgreSQL services that need additional steps. We are monitoring the situation closely and will continue until all affected services are healthy. --- [2026-10-20T11:10:25Z] (investigating) The latest information identifies `europe-west2` and the `europe-west2-b` zone as affected locations. The incident involves Virtual Private Cloud (VPC) networking issues that are disrupting communication between virtual machines in the affected location, which is impacting the availability of clustered Aiven services — currently Aiven for Apache Kafka and Aiven for OpenSearch. We continue to monitor our services to identify any remaining impacted services and we are waiting for connectivity to be restored from Google side, and for the affected nodes to return. We will share further updates as more information becomes available. --- [2026-10-20T08:44:19Z] (investigating) The latest information identifies europe-west2 and the europe-west2-b zone as affected locations. The incident involves Virtual Private Cloud (VPC) networking issues that can disrupt communication between virtual machines. This may affect connectivity between nodes and the availability of clustered Aiven services in the affected location. Our team continues to investigate the impact on affected services and monitor their health. We will share further updates as more information becomes available. --- [2026-10-20T06:51:36Z] (investigating) We are investigating an ongoing Google Cloud networking incident. Google Cloud engineers have confirmed an issue with Virtual Private Cloud (VPC) networking affecting communication between virtual machines, including communication over internal IP addresses, IPv6, and other networking paths. ``` The incident is currently reported to affect the following regions: Africa: africa-south1 Europe: europe-central2, europe-north1, europe-north2, europe-southwest1, europe-west1, europe-west2, europe-west3, europe-west4, europe-west6, europe-west8, europe-west9, europe-west10, and europe-west12 ``` This issue is impacting network connectivity between nodes and may affect the availability and performance of clustered Aiven services in the affected regions. Our team is investigating the impact and monitoring affected services. We will provide further updates as more information becomes available. --- [2026-10-20T06:43:23Z] (investigating) We are investigating an ongoing Google Cloud VPN incident affecting the europe-west2 and africa-south1 regions. This is impacting network connectivity between nodes and may affect the availability and performance of clustered Aiven services in the affected regions. Our team is investigating the impact and monitoring affected services. We will provide further updates as more information becomes available.

We have resolved the underlying issues of nodes creation and replacement in the **vultr-ewr** cloud region. 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. --- [2026-10-18T10:54:17Z] (investigating) Creation and replacement of nodes in the **vultr-ewr** cloud region are experiencing issues and may take longer than normal to come up. Services that are already running are not affected. Our engineering team is actively working on this, and we will provide another update as soon as we have more information.

This incident has been resolved. New service nodes are able to start normally again, and running nodes were not affected at any point during the incident. We apologize for any inconvenience this may have caused. --- [2026-10-16T09:56:54Z] (monitoring) A fix has been implemented and we are currently monitoring the results. New service nodes are able to start again, and running nodes were not affected at any point. We will provide further updates once we have confirmed the issue is fully resolved. --- [2026-10-16T08:40:11Z] (investigating) We are currently experiencing an issue with starting new service nodes for almost all service types. The running nodes are not affected. Our engineering team is actively working on a fix and we will provide another update as soon as we have more information.