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-23 23:17 UTC
Public — what happened
Summary
Confluent Cloud reported a major incident in which its Cloud Console was degraded across all regions and several services in the AWS us-west-2 region were affected. The problem began on 2026-09-23 at 11:47 UTC and was marked resolved at 23:17 the same day. Confluent Cloud said all impacted services had recovered, that customers did not need to take any steps, and it did not share a cause in the update provided.
Timeline
- Started — 2026-09-23 11:47 UTC
- Resolved — 2026-09-23 23:17 UTC · 11h 30m 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.