Major incident
Confluent Cloud: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Sep 23, 2026, 11:47 UTC
started
23:17 UTC
resolved
11 h 30 min
duration
Affected: Confluent Cloud
Current status of Confluent Cloud: Operational — live Confluent Cloud status
Timeline
- Sep 23, 2026, 11:47 UTCidentifiedThe issue has been identified and a fix is being implemented.
- Sep 23, 2026, 14:18 UTCidentifiedFlink in AWS us-west-2 is continues to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. All other services including Connect, ConfluentCloud UI are mitigated and operational
- Sep 23, 2026, 15:57 UTCmonitoringAll affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.
- Sep 23, 2026, 23:17 UTCresolvedThis incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Updates as published by Confluent Cloud (original).
Other services with incidents at the same time
This was part of a wider event: 24 services reported incidents within the hour.
- Sanity 10:54 UTC · Content Agent - Elevated error rates
- Buffer 10:52 UTC · Issue Connecting and Refreshing Threads
- DAT Freight & Analytics 10:51 UTC · DAT Keypoint Login Issues
More Confluent Cloud incidents
- October 20, 2026 Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- October 16, 2026 Delay in Kafka cluster provisioning
- October 15, 2026 Confluent Cloud Console (UI) degraded functionality
- October 9, 2026 Possible outage in AWS us-east-1
- October 9, 2026 Experiencing high error rate in AZURE in West Europe region
- October 8, 2026 Experiencing high error rate in AZURE in Germany West Central region