Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Sep 23, 11:47 UTCSep 23, 23:17 UTC
Duration
11h 30m
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
20 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Timeline
- Resolved · Sep 23, 23:17 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.
- Monitoring · Sep 23, 15:57 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.
- Identified · Sep 23, 14:18 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
- Identified · Sep 23, 11:47 UTC
The issue has been identified and a fix is being implemented.
More from Confluent
Full historyKafka - Increased latency and connectivity issues - Azure - brazilsouthlasted 2h 9mMultiple Confluent Cloud services are in a degraded state - GCP EU-West2lasted 10h 25mDelay in Kafka cluster provisioninglasted 7h 18mConfluent Cloud Console (UI) degraded functionalitylasted 2h 45mPossible outage in AWS us-east-1lasted 56mExperiencing high error rate in AZURE in West Europe regionlasted 20h 2m