Confluent Cloud
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
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

About This Site

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.

Confluent Cloud Degraded Performance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

New Intermediate TLS Certificates rollout starting May 13th, 2026 May 13, 2026 00:00 - Jun 12, 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.

Learn more at https://support.confluent.io/hc/en-us/articles/45269123919252-New-Intermediate-TLS-Certificates-rollout-starting-May-13th-2026

Apr 01, 2026 - 16:51 UTC
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.

Learn more at https://support.confluent.io/hc/en-us/articles/45269123919252-New-Intermediate-TLS-Certificates-rollout-starting-May-13th-2026

Mar 13, 2026 - 21:45 UTC
May 9, 2026

No incidents reported today.

May 8, 2026

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

May 7, 2026
Resolved - The maintenance is complete.
May 7, 03:08 UTC
Monitoring - Confluent Cloud is undergoing a planned maintenance event between 4pm and 8pm PST on May 6, 2026. Customers might experience intermittent unavailability of certain pages in the customer portal, such as new customer sign-up, cluster creation, promo code claims, invoicing and public cost interfaces.
May 6, 22:12 UTC
May 6, 2026
May 5, 2026

No incidents reported.

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Apr 30, 2026

No incidents reported.

Apr 29, 2026

No incidents reported.

Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026
Resolved - This incident has been resolved.
Apr 25, 00:14 UTC
Monitoring - A fix has been implemented and we are monitoring for next hour.
Apr 24, 23:06 UTC
Update - Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.
Apr 24, 22:27 UTC
Identified - The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.
Apr 24, 20:14 UTC
Investigating - We are currently investigating this issue.
Apr 24, 17:18 UTC