rewindex

ChangesAivenGoogle Cloud VPN incident affecting services

Aiven: Incident updated: Google Cloud VPN incident affecting services

Incident updateNot classified yetChanged status.aiven.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

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…”

See the cascade chart and every vendor →

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.

What changed

Struck in red is what Aiven removed; blue is what they added. Muted text is unchanged context.

AddedUpdateinvestigating#1
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

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

History of this incident

YesterdayTuesday, October 20Tue, Oct 20

6 incident changes

All Aiven changesAiven profileMarkdownJSON