Confluent incident
Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
Confluent experienced a major incident on May 8, 2026 affecting Confluent Cloud, lasting 27d 15h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 01:14 AM UTC
We are investigating data plane impact (produce/consume) resulting from elevated error rates and latencies from AWS us-east-1 resources in AZ4. EC2 instances hosted on this availability zone are impaired by loss of power during an ongoing thermal event.
- monitoring May 08, 2026, 01:55 AM UTC
We are monitoring the health of impacted brokers in the affected availability zone. More details about the thermal event on the AWS status page: https://health.aws.amazon.com/health/status
- monitoring May 09, 2026, 01:19 PM UTC
AWS has resolved the underlying infrastructure issue in us-east-1 (use1-az4). The majority of Confluent Cloud services have recovered and are operating normally. We are continuing to monitor for any lingering effects and performing cleanup of affected resources.
- monitoring May 12, 2026, 06:51 PM UTC
AWS has reported the underlying infrastructure issue in us-east-1 (use1-az4) as resolved. However, some Confluent Cloud customers in the affected availability zone continue to experience connectivity issues. Confluent is actively investigating and working to restore full connectivity for impacted customers.
- resolved Jun 04, 2026, 04:47 PM UTC
The incident has been resolved and us-east-1 (use1-az4) is fully operational.