Confluent incident
Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Resolved after 11 hours 29 minutes, affecting Confluent Cloud, on September 23, 2026.
This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Affected components
Update timeline
- identified Sep 23, 2026, 11:47 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 23, 2026, 02:18 PM UTC
Flink 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
- monitoring Sep 23, 2026, 03:57 PM UTC
All 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.
- resolved Sep 23, 2026, 11:17 PM UTC
This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Your product runs on more than Confluent
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services