Live / Confluent Cloud / Incident
Confluent Cloud: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Confluent Cloud · confluent.cloudMajor incidentResolved2026-09-22 01:31 UTC
Public — what happened
Summary
Confluent Cloud reported a major incident beginning on 2026-09-21 at 16:04 UTC in which its Cloud Console was degraded across all regions and several services in the AWS us-west-2 region were affected. The company said everything impacted, including its Flink service in us-west-2, had recovered by 01:31 on 2026-09-22. Confluent Cloud did not give a cause in its update, and said customers did not need to take any steps and should see no further disruption.
Timeline
- Started — 2026-09-21 16:04 UTC
- Resolved — 2026-09-22 01:31 UTC · 9h 27m 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 40, 2026, our weekly internet health report.