Confluent: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
Multiple Confluent Cloud services were degraded in GCP EU-West2, with major impact; some customers could experience service issues. The incident began at 2026-10-20 08:02 UTC and remained open when archived, open for 0 min at the last update. Confluent was investigating and attributed the disruption to ongoing GCP EU-West2 issues.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents
Confluent’s incident blames Google Cloud as the cause. (hop 1, posted +8 h 39 min vs Google Cloud’s own post)
“…Multiple Confluent Cloud services are in a degraded state - GCP EU-West2 This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally. Some cus…”
Swipe sideways to see the whole diagram.
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["Confluent (this incident)<br/>posted +8 h 39 min"]:::me
later --- meFull 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: Confluent Cloud
Timeline of updates
- investigating
Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2
- investigating
We are currently working to restore the impacted services. Most customers should be able to use Confluent Cloud services normally.
- monitoring
The underlying GCP issue has been mitigated. Confluent Cloud Kafka clusters in the affected zone are fully operational and Connect and Flink workloads have recovered. We are monitoring to confirm stability and working to restore the few remaining impacted resources.
- monitoring
We are continuing to monitor for any further issues.
- resolved
This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.
Changes Rewindex caught on this incident
- Incident updated: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- Major incident: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- Incident updated: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- Incident updated: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
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 stspg.io (opens in new tab).