Live / Confluent Cloud / Incident
Confluent Cloud: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
Confluent Cloud · confluent.cloudMajor incidentResolved2026-10-20 18:27 UTC
Public — what happened
Summary
Confluent Cloud said that starting at 08:02 UTC on 2026-10-20, some customers could have trouble with its services in the GCP EU-West2 region, and it attributed this to an ongoing problem at Google Cloud. By 12:55 UTC it said it was working to restore the affected services and that most customers could use them normally. At 14:46 UTC it said the underlying Google Cloud issue had been mitigated, its Kafka clusters in the affected zone were fully operational, and Connect and Flink workloads had recovered, with a few remaining resources still being restored. The incident was marked resolved at 18:27 UTC after a period of monitoring.
Affected
Confluent Cloud
Timeline
- Started — 2026-10-20 08:02 UTC
- Investigating — 2026-10-20 08:02 UTC (2 updates)
- Monitoring — 2026-10-20 14:46 UTC (2 updates)
- Resolved — 2026-10-20 18:27 UTC · 10h 25m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Confluent Cloud report →
More from Confluent Cloud
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.