rewindex

CompaniesAivenIncidents

Aiven: Google Cloud VPN incident affecting services

MinorStatus: resolvededitedStarted Resolved (13 h)8 updatesstatus.aiven.io (opens in new tab)
Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents

Aiven’s incident blames Google Cloud as the cause. (hop 1, posted +35 min vs Google Cloud’s own post)

“…Google Cloud VPN incident affecting services 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 a…”

Swipe sideways to see the whole diagram.

Google Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed Google CloudJFrogWithin an hour4 vendors, 4 blamed Google CloudAiven, Northflank, Elastic Cloud, dbt Labs1 to 4 hours later4 vendors, 4 blamed Google CloudMongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse CloudLater2 vendors, 1 blamed Google CloudGrafana Cloud, ConfluentAiven (this incident)posted +35 min
Google Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed GoogleCloudJFrogWithin an hour4 vendors, 4 blamed GoogleCloudAiven, Northflank, Elastic Cloud,dbt Labs1 to 4 hours later4 vendors, 4 blamed GoogleCloudMongoDB Atlas, Sourcegraph,CockroachDB, ClickHouseCloudLater2 vendors, 1 blamed GoogleCloudGrafana Cloud, ConfluentAiven (this incident)posted +35 min
Aiven is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud europe-west2<br/>posted 06:08 UTC"]:::root
  before["Posted before Google Cloud did<br/>1 vendor, 1 blamed Google Cloud<br/>JFrog"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed Google Cloud<br/>Aiven, Northflank, Elastic Cloud, dbt Labs"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Google Cloud<br/>MongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 1 blamed Google Cloud<br/>Grafana Cloud, Confluent"]:::blames
  root --> later
  me["Aiven (this incident)<br/>posted +35 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Aiven

Timeline of updates

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. resolved

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.aiven.io (opens in new tab).

Aiven profileRecent Aiven incidentsMarkdownJSON