Search

Companies / Confluent / incidents

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

Impact: majorStatus: resolvedStarted Resolved (28 d)5 updatesSource: stspg.io (opens in new tab)
Summary

Confluent Cloud reported a major incident affecting produce/consume operations in AWS us-east-1 AZ4, with elevated errors, latency and lingering connectivity issues. It started 2026-05-08 01:14 UTC and resolved 2026-06-04 16:47 UTC, lasting 27 days 15 h. Confluent attributed the initial impact to EC2 power loss during a thermal event and confirmed full operation at resolution.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Confluent Cloud

Timeline of updates

  1. 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. 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. 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. 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. resolved

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

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON