Confluent Cloud incident: Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2

Affected components

• Confluent Cloud

1. resolvedJun 21, 2026, 09:19 UTC

   This incident has been resolved.

2. monitoringJun 21, 2026, 09:19 UTC

   We are continuing to monitor for any further issues.

3. monitoringJun 21, 2026, 08:31 UTC

   The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.

4. identifiedJun 21, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snyk: Data Freshness delay in Issues API for customers on app.snyk.ioMinor · Jun 16, 2026, 04:52 UTC
• Smartsheet: Increased spam activity with Smartsheet FormsMinor · Jun 18, 2026, 21:42 UTC
• Snyk: Third-Party Vendor Security Incident (Klue)Minor · Jun 19, 2026, 23:15 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history