Major incident
Confluent Cloud: Connectivity degradation - AWS us-east-1
Sep 8, 2026, 20:01 UTC
started
13:01 UTC
resolved September 9, 2026
17 h
duration
Affected: Confluent Cloud
Current status of Confluent Cloud: Operational — live Confluent Cloud status
Timeline
- Sep 8, 2026, 20:01 UTCinvestigatingWe are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.
- Sep 8, 2026, 20:13 UTCinvestigatingWe are continuing to investigate this issue.
- Sep 8, 2026, 20:20 UTCidentifiedA possible root cause has been identified and the Confluent Cloud team is implementing a fix
- Sep 8, 2026, 20:30 UTCmonitoringA fix has been implemented and the team is monitoring recovery.
- Sep 9, 2026, 13:01 UTCresolvedThe issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.
Updates as published by Confluent Cloud (original).
Other services with incidents at the same time
This was part of a wider event: 74 services reported incidents within the hour.
- ngrok 20:05 UTC · Error when signing in via SSO
- Kaseya 19:43 UTC · Datto BCDR - Server5465 (US-East) - Degraded Node Functionality
- Miro 19:21 UTC · Sign-in with username and password is unavailable
- Kaseya 19:10 UTC · Datto BCDR - Server2214 (US-East) - Degraded Node Functionality
- ngrok 19:01 UTC · Endpoints using traffic policies are erroneously hitting limits
More Confluent Cloud incidents
- October 20, 2026 Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- October 16, 2026 Delay in Kafka cluster provisioning
- October 15, 2026 Confluent Cloud Console (UI) degraded functionality
- October 9, 2026 Possible outage in AWS us-east-1
- October 9, 2026 Experiencing high error rate in AZURE in West Europe region
- October 8, 2026 Experiencing high error rate in AZURE in Germany West Central region