Confluent Cloud incident: Kafka cluster performance degradation for clusters in AWS region eu-central-1

Affected components

• Confluent Cloud

1. resolvedJul 16, 2026, 13:14 UTC

   The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.

2. investigatingJul 15, 2026, 23:33 UTC

   Confluent is aware of the ongoing AWS incident affecting eu-central-1. We have identified degraded performance impacting clusters in this region, and our engineers are actively working with AWS to mitigate the issue.

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.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Tailscale: Admin console and pkgs.tailscale.com are unavailableCritical · Jul 16, 2026, 08:13 UTC
• Supabase: Projects in stuck state in EU-CENTRAL-1 (Frankfurt)Major · Jul 16, 2026, 07:00 UTC
• Vercel: SAML Single Sign-On (SSO) errorsMajor · Jul 16, 2026, 08:39 UTC
• Plaid: Elevated dashboard.plaid.com error ratesMajor · Jul 16, 2026, 08:48 UTC
• RevenueCat: Some users unable to login via single-sign-on (SSO)Major · Jul 16, 2026, 09:13 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Vercel: Errors accessing teams that require 2FAMinor · Jul 15, 2026, 23:04 UTC
• ClickHouse Cloud: AWS eu-central-1 performance degradationMinor · Jul 15, 2026, 23:33 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 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