What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Confluent Cloud now? Check the current statusAffected services
Updates (4)
- Sep 23, 2026, 11:17 PMConfluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Confluent Cloud ↗ - Sep 23, 2026, 03:57 PMConfluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
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.
Confluent Cloud ↗ - Sep 23, 2026, 02:18 PMConfluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
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
Confluent Cloud ↗ - Sep 23, 2026, 11:47 AMConfluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
The issue has been identified and a fix is being implemented.
Confluent Cloud ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Confluent Cloud's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.