Confluent Cloud outage: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4

Affected components

• Confluent Cloud

1. resolvedJun 4, 2026, 16:47 UTC

   The incident has been resolved and us-east-1 (use1-az4) is fully operational.

2. monitoringMay 12, 2026, 18:51 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.

3. monitoringMay 9, 2026, 13:19 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 verifying full service restoration.

4. monitoringMay 8, 2026, 01:55 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

5. investigatingMay 8, 2026, 01:14 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.

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.

• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Upstash: QStash US Region Service DisruptionCritical · May 8, 2026, 09:46 UTC
• Upstash: Fly.io Upstash Redis Service DistruptionCritical · May 12, 2026, 09:49 UTC
• Confluence: Users experiencing issues accessing multiple Atlassian productsCritical · May 14, 2026, 04:54 UTC
• Bitbucket: Users experiencing issues accessing multiple Atlassian productsCritical · May 14, 2026, 05:03 UTC
• Datadog: Azure Metrics ReportingCritical · May 16, 2026, 02:17 UTC
• Netlify: Elevated response times affecting origin servicesCritical · May 19, 2026, 21:08 UTC
• Mailgun: Delayed sending in EUCritical · May 25, 2026, 12:18 UTC
• ReadMe: ReadMe Refactored OutageCritical · May 27, 2026, 17:08 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