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
Confluent Cloud
Updates (4)
- Jun 21, 2026, 09:19 AMKafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
This incident has been resolved.
Confluent Cloud ↗ - Jun 21, 2026, 09:19 AMKafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
We are continuing to monitor for any further issues.
Confluent Cloud ↗ - Jun 21, 2026, 08:31 AMKafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.
Confluent Cloud ↗ - Jun 21, 2026, 07:14 AMKafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
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.
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.