Update - 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.
May 12, 2026 - 18:51 UTC
Update - 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.
May 09, 2026 - 13:19 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
May 08, 2026 - 01:55 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.
May 08, 2026 - 01:14 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 2026 - 00:00 UTC
Update - Starting May 13, 2026, TLS certificates used to connect to Confluent Cloud will start using new intermediate certificates provided by Let's Encrypt.
No downtime is expected.
No action is needed if you haven't pinned intermediate certificates. However, if you've pinned intermediate certificates, you need to update your clients' certificates before May 13th or remove the intermediate certificate pinning to avoid connection issues.
Scheduled - Starting May 13, 2026, TLS certificates used to connect to Confluent Cloud will start using new intermediate certificates provided by Let's Encrypt.
No downtime is expected.
No action is needed if you haven't pinned intermediate certificates. However, if you've pinned intermediate certificates, you need to update your clients' certificates before May 13th or remove the intermediate certificate pinning to avoid connection issues.
Update - Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
Apr 02, 2026 - 15:40 UTC
Update - Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
Apr 01, 2026 - 19:52 UTC
Monitoring - AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
Mar 20, 2026 - 13:58 UTC
Welcome to Confluent Cloud's status page. Here you will find high level availability information for the Confluent Cloud managed service. Visit https://confluent.cloud to manage your Confluent Cloud clusters.
Resolved -
The incident has been resolved.
May 22, 00:22 UTC
Investigating -
Starting 20:26 UTC May 21, 2026, Confluent Cloud experienced connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2. We have fully mitigated the issue as of 23:56 UTC May 21, 2026 and service is operating normally.
May 22, 00:21 UTC
May 21, 2026
No incidents reported.
May 20, 2026
No incidents reported.
May 19, 2026
No incidents reported.
May 18, 2026
No incidents reported.
May 17, 2026
No incidents reported.
May 16, 2026
No incidents reported.
May 15, 2026
Unresolved incident: New Intermediate TLS Certificates rollout starting May 13th, 2026.