Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
Jun 21, 07:14 UTCJun 21, 09:19 UTC
Duration
2h 5m
Impact
Minor
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved.
Timeline
- Resolved · Jun 21, 09:19 UTC
This incident has been resolved.
- Monitoring · Jun 21, 09:19 UTC
We are continuing to monitor for any further issues.
- Monitoring · Jun 21, 08:31 UTC
The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.
- Identified · Jun 21, 07:14 UTC
The team has identified the root cause of the issues affecting standard and basic Kafka clusters in the AWS us-east-2 region. We are actively working on a mitigation strategy and will provide further updates as they become available.
More from Confluent
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2311:47 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 11h 30m |
| Sep 2215:09 UTC | Elevated error rates in Azure Germany West Central region | major | 4h 50m |
| Sep 2116:15 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 9h 16m |
| Sep 1717:49 UTC | Confluent Cloud Metrics API experienced elevated latency and error rates | none | 0m |
| Sep 1523:59 UTC | Multiple Confluent Cloud services are in a degraded state - All regions | major | 1h 22m |
| Sep 820:01 UTC | Connectivity degradation - AWS us-east-1 | major | 17h |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.