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
Updates (5)
- Jun 4, 2026, 04:47 PMElevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
The incident has been resolved and us-east-1 (use1-az4) is fully operational.
Confluent Cloud ↗ - May 12, 2026, 06:51 PMElevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
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.
Confluent Cloud ↗ - May 9, 2026, 01:19 PMElevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
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 verifying full service restoration.
Confluent Cloud ↗ - May 8, 2026, 01:55 AMElevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
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
Confluent Cloud ↗ - May 8, 2026, 01:14 AMElevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
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.
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.