Major incident

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

May 8, 2026, 01:14 UTC
started
16:47 UTC
resolved June 4, 2026
27 days 15 h
duration

Affected: Confluent Cloud

Current status of Confluent Cloud: Operational — live Confluent Cloud status

Timeline

  1. May 8, 2026, 01:14 UTC
    investigating
    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.
  2. May 8, 2026, 01:55 UTC
    monitoring
    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
  3. May 9, 2026, 13:19 UTC
    monitoring
    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. May 12, 2026, 18:51 UTC
    monitoring
    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.
  5. Jun 4, 2026, 16:47 UTC
    resolved
    The incident has been resolved and us-east-1 (use1-az4) is fully operational.

Updates as published by Confluent Cloud (original).

Other services with incidents at the same time

This was part of a wider event: 61 services reported incidents within the hour.

More Confluent Cloud incidents