Sep <var data-var='date'>27</var>, <var data-var='time'>02:00</var> UTC Resolved - Confluent Cloud Metrics were delayed from 00:33 to 02:15 UTC on Sep 27. Queries for recent metrics during this time duration may return incomplete or no data. This incident has been resolved as of 02:15 UTC.

Missing Metrics on Confluent Cloud

Sep <var data-var='date'>26</var>, <var data-var='time'>19:43</var> UTC Resolved - This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers. Sep <var data-var='date'>26</var>, <var data-var='time'>19:43</var> UTC Update - We are continuing to work on a fix for this issue. Sep <var data-var='date'>26</var>, <var data-var='time'>13:23</var> UTC Update - Systems are continuing to recover and are being monitored Sep <var data-var='date'>26</var>, <var data-var='time'>08:00</var> UTC Identified - Microsoft Azure has confirmed an outage impacting their Azure East US region, which is the root cause of the elevated error rates affecting Confluent services. Confluent will provide another update as soon as we receive further details. Sep <var data-var='date'>26</var>, <var data-var='time'>06:40</var> UTC Investigating - We are currently investigating an issue related to elevated error rates in Azure East US

Elevated error rates in Azure East US

Sep <var data-var='date'>23</var>, <var data-var='time'>23:17</var> UTC Resolved - This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers. Sep <var data-var='date'>23</var>, <var data-var='time'>15:57</var> UTC Monitoring - All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident. Sep <var data-var='date'>23</var>, <var data-var='time'>14:18</var> UTC Update - Flink in AWS us-west-2 is continues to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. All other services including Connect, ConfluentCloud UI are mitigated and operational Sep <var data-var='date'>23</var>, <var data-var='time'>11:47</var> UTC Identified - The issue has been identified and a fix is being implemented.

Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

Sep <var data-var='date'>22</var>, <var data-var='time'>19:58</var> UTC Resolved - This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational. Sep <var data-var='date'>22</var>, <var data-var='time'>19:35</var> UTC Monitoring - The Azure regional disruption has ended, and Confluent Cloud mitigation was achieved as of 18:00 UTC. Clusters in the Azure's Germany West Central region are now fully operational. We will monitor for residual impact before marking this incident resolved. Sep <var data-var='date'>22</var>, <var data-var='time'>15:09</var> UTC Investigating - We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in Microsoft Azure's Germany West Central region, beginning at approximately 13:00 UTC on 22 Sep 2026. Affected customers may experience degraded availability or intermittent connectivity for clusters in the region. This is associated with an ongoing Microsoft Azure service disruption in that region. We are actively engaged with Microsoft Azure.

Elevated error rates in Azure Germany West Central region

Sep <var data-var='date'>22</var>, <var data-var='time'>01:31</var> UTC Resolved - This incident has been resolved. All affected services, including Flink in AWS us-west-2, have fully recovered, and no further customer impact is expected. No action is required from customers. Sep <var data-var='date'>22</var>, <var data-var='time'>00:40</var> UTC Monitoring - All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident. Sep <var data-var='date'>22</var>, <var data-var='time'>00:06</var> UTC Update - Confluent is continuing to monitor recovered services and complete recovery for a small number of Flink customers in AWS us-west-2 that may still be experiencing degraded jobs. We are actively working to fully restore them and will post the next update by 00:30 UTC, or sooner if service is fully restored. Sep <var data-var='date'>21</var>, <var data-var='time'>23:35</var> UTC Update - All affected services have recovered with the exception of a small number of Flink customers in AWS us-west-2 that may still experience degraded jobs while we complete recovery. We are actively working to fully restore them and will post the next update by 00:00 UTC, or sooner if service is fully restored. Sep <var data-var='date'>21</var>, <var data-var='time'>23:06</var> UTC Update - Flink in AWS us-west-2 is still recovering as we continue to restore full service: while some jobs may start to recover, others may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 23:30 UTC or sooner if recovery completes sooner. Sep <var data-var='date'>21</var>, <var data-var='time'>22:12</var> UTC Update - Flink in AWS us-west-2 is still recovering as we continue to restore full service: running jobs may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 22:30 UTC or sooner if recovery completes sooner. Sep <var data-var='date'>21</var>, <var data-var='time'>21:30</var> UTC Update - Most affected services are recovering and we are continuing to monitor for stability. Flink in AWS us-west-2 is still recovering and running jobs may remain degraded with new submissions still failing. We will post the next update by 22:00 UTC or sooner if the situation changes. Sep <var data-var='date'>21</var>, <var data-var='time'>20:56</var> UTC Identified - We have applied a mitigation and most affected services are beginning to recover. Flink in AWS us-west-2 will continue to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. We will post the next update by 21:30 UTC, or sooner if service is restored. Sep <var data-var='date'>21</var>, <var data-var='time'>20:03</var> UTC Update - We are continuing to work to resolve the incident and do not yet have a confirmed mitigation. Impact remains as previously described. We will post the next update by 20:30 UTC, or sooner if the situation changes. Sep <var data-var='date'>21</var>, <var data-var='time'>19:33</var> UTC Update - We are continuing to validate several proposed mitigations to address the ongoing incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. We do not yet have a confirmed fix in place. We will post the next update by 20:00 UTC, or sooner if service is restored. Sep <var data-var='date'>21</var>, <var data-var='time'>19:08</var> UTC Update - We are continuing to investigate an incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. Several potential mitigations remain under active testing and validation. We do not yet have a confirmed fix in place. We will post the next update by 19:30 UTC, or sooner if service is restored. Sep <var data-var='date'>21</var>, <var data-var='time'>18:31</var> UTC Update - We are testing and validating several potential mitigations in parallel to restore the Confluent Cloud Console and affected services. We do not yet have a confirmed fix in place and are continuing to investigate. We will post the next update by 19:00 UTC, or sooner if service is restored. Sep <var data-var='date'>21</var>, <var data-var='time'>18:01</var> UTC Update - We have refined the scope of customer impact and continue to work on a mitigation. Impacted Services: - Confluent Cloud Console (web UI), all regions: broad degradation. Customers may be unable to view or manage their resources in the Console. - Schema Registry, AWS us-west-2: a subset of Schema Registry clusters are unavailable. - Flink, AWS us-west-2: all running jobs are degraded, and new job submissions will fail. - Cluster Linking, AWS us-west-2: links to Enterprise clusters are impacted. - Topic operations, AWS us-west-2: unavailable for Freight and some Basic and Standard clusters. - Tableflow, AWS us-west-2: All operations are unavailable (additionally, topics utilizing the us-west-2 Schema Registry may be impacted) - Connect, AWS us-west-2: Some connectors dependent on unavailable Schema Registry clusters may be affected - Notifications, all regions: delivery is delayed. Customers may not receive notifications and alerts until the backlog clears. Confirmed not impacted: - Regular produce and consume operations on Kafka clusters are not affected. - Topic-related operations on Enterprise and Dedicated clusters are not affected. We are actively applying a mitigation. We will post the next update by 18:30 UTC, or sooner if service is restored. Sep <var data-var='date'>21</var>, <var data-var='time'>17:04</var> UTC Update - We are confirming a contributing factor and applying a mitigation intended to restore Confluent Cloud services. We will post an update by 17:45 UTC, or sooner if service is restored. Sep <var data-var='date'>21</var>, <var data-var='time'>16:32</var> UTC Update - We have made progress in identifying the cause of the disruption in AWS us-west-2 and are working to confirm the safest path to mitigation. Some customers in this region may continue to experience errors or degraded performance. We will post the next update by 17:00 UTC, or sooner if mitigation is achieved. Sep <var data-var='date'>21</var>, <var data-var='time'>16:15</var> UTC Update - Multiple Confluent Cloud services in the AWS us-west-2 region are experiencing elevated error rates and service disruption. Impacted customers may see failed or slow requests to Kafka clusters, Connect, and Flink in this region. The Confluent Cloud UI is also degraded and visibility to clusters outside of us-west-2 may be impacted as well. We are actively investigating and will post the next update by 16:30 UTC, or sooner if we have new information. Sep <var data-var='date'>21</var>, <var data-var='time'>16:04</var> UTC Investigating - Starting today at 15:26 UTC, Confluent Cloud is experiencing an incident involving multiple service disruptions in the AWS us-west-2 region. We are investigating the issue and will provide further updates shortly.

Sep <var data-var='date'>17</var>, <var data-var='time'>17:00</var> UTC Resolved - Confluent Cloud Metrics API experienced elevated latency and error rates between 9:55 AM PDT to 10:10 AM PDT.

Confluent Cloud Metrics API experienced elevated latency and error rates

Sep <var data-var='date'>16</var>, <var data-var='time'>01:21</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>16</var>, <var data-var='time'>00:22</var> UTC Monitoring - The mitigation has been deployed and the degraded services are recovering as of 00:20 UTC on September 16th, 2026. We'll continue to monitor for any residual issues before resolving this incident in 1 hour (01:20 UTC). Sep <var data-var='date'>16</var>, <var data-var='time'>00:00</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>15</var>, <var data-var='time'>23:59</var> UTC Investigating - Starting on Tuesday, September 15th 2026 at 21:25 UTC, multiple Confluent Cloud services began entering a degraded state. We have identified the cause of the degradation and are actively mitigating the issue. Updates will be posted here in the next 30 minutes or when the issue is fully mitigated, whichever happens first.

Multiple Confluent Cloud services are in a degraded state - All regions

Sep <var data-var='date'> 9</var>, <var data-var='time'>14:56</var> UTC Resolved - The systems have recovered and Confluent Cloud is fully operational. Sep <var data-var='date'> 9</var>, <var data-var='time'>06:41</var> UTC Monitoring - We have applied a mitigation for the issue affecting Schema Registry, Authentication, ksqlDB, Flink, and Kafka operations in AWS us-east-1. Services are recovering and we are monitoring closely. Sep <var data-var='date'> 9</var>, <var data-var='time'>01:45</var> UTC Update - Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available. Sep <var data-var='date'> 9</var>, <var data-var='time'>00:01</var> UTC Update - Confluent is continuing to work on remediating the service disruption in AWS us-east-1. Sep <var data-var='date'> 8</var>, <var data-var='time'>17:41</var> UTC Update - We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time. Sep <var data-var='date'> 8</var>, <var data-var='time'>15:55</var> UTC Update - We continue to work on remediating the service disruption in AWS us-east-1. Confirmed impact: - Authentication — a subset of requests may fail - Schema Registry — authorization errors on a subset of requests - ksqlDB — a subset of queries/requests may be affected - Flink — statement management operations (create/update/delete) are degraded, and some running Flink jobs may fail or restart - Kafka operations (create, delete etc) Not impacted: Kafka cluster data-plane operations are not affected by this incident. This issue is isolated to the AWS us-east-1 region; other regions are unaffected Sep <var data-var='date'> 8</var>, <var data-var='time'>14:06</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'> 8</var>, <var data-var='time'>11:38</var> UTC Investigating - We are currently investigating this issue. Sep <var data-var='date'> 8</var>, <var data-var='time'>10:37</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'> 8</var>, <var data-var='time'>09:17</var> UTC Investigating - We are investigating a service disruption affecting multiple services in AWS us-east-1 region. Affected customers may experience authentication failures, errors accessing Schema Registry, or issues with KSQL and Flink workloads. We are actively investigating the root cause and working toward mitigation.

Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1

Sep <var data-var='date'> 9</var>, <var data-var='time'>13:01</var> UTC Resolved - The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational. Sep <var data-var='date'> 8</var>, <var data-var='time'>20:30</var> UTC Monitoring - A fix has been implemented and the team is monitoring recovery. Sep <var data-var='date'> 8</var>, <var data-var='time'>20:20</var> UTC Identified - A possible root cause has been identified and the Confluent Cloud team is implementing a fix Sep <var data-var='date'> 8</var>, <var data-var='time'>20:13</var> UTC Update - We are continuing to investigate this issue. Sep <var data-var='date'> 8</var>, <var data-var='time'>20:01</var> UTC Investigating - We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.

Connectivity degradation - AWS us-east-1

Sep <var data-var='date'> 1</var>, <var data-var='time'>17:14</var> UTC Resolved - The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels. Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support. Sep <var data-var='date'> 1</var>, <var data-var='time'>16:27</var> UTC Investigating - We are investigating elevated error rates and degraded performance for some services running in the Google Cloud (GCP) us-central1 region. This is related to an ongoing Google Cloud networking issue affecting a portion of the region. Customers in this region may experience issues provisioning or deprovisioning clusters, intermittent connectivity issues, elevated latency, or errors. We are actively assessing the full scope of impact and will provide an update as more information becomes available.

Investigating Elevated Errors in GCP us-central1

Aug <var data-var='date'>25</var>, <var data-var='time'>07:29</var> UTC Resolved - Confluent services in the Azure Southeast Asia region are now healthy and operating normally. Aug <var data-var='date'>25</var>, <var data-var='time'>05:28</var> UTC Monitoring - We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation. Aug <var data-var='date'>25</var>, <var data-var='time'>04:17</var> UTC Investigating - We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in the Azure Southeast Asia region, beginning at approximately 03:13 UTC on 25 Aug 2026. Affected customers may experience degraded produce/consume availability or intermittent connectivity for clusters in this region. This is associated with an ongoing Microsoft Azure service disruption in the Southeast Asia region. We are actively engaged with Microsoft Azure.

Elevated error rates and latencies in Azure Southeast Asia region

Aug <var data-var='date'>23</var>, <var data-var='time'>21:00</var> UTC Resolved - Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.

Confluent Cloud logging degradation - Connect and Flink

Aug <var data-var='date'>20</var>, <var data-var='time'>20:18</var> UTC Resolved - The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring. Aug <var data-var='date'>20</var>, <var data-var='time'>19:18</var> UTC Update - We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour. Aug <var data-var='date'>20</var>, <var data-var='time'>17:10</var> UTC Investigating - We are investigating an incident affecting services in the GCP us-west1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates. Our engineering teams are actively working to restore normal performance.

Elevated error rates and latency in GCP us-west1

Jul <var data-var='date'>18</var>, <var data-var='time'>00:59</var> UTC Resolved - All the statements should be running now. Jul <var data-var='date'>17</var>, <var data-var='time'>22:55</var> UTC Monitoring - Currently, we are monitoring the results after rolling out the fix. Jul <var data-var='date'>17</var>, <var data-var='time'>22:54</var> UTC Identified - Engineers have identified and implemented a fix. Jul <var data-var='date'>17</var>, <var data-var='time'>22:01</var> UTC Investigating - Flink statements are degraded in GCP us-central1 region. The impact started at 18:37 UTC on July 17. Currently, engineers are investigating the issue.

Flink statements degraded in GCP us-central1 region

Jul <var data-var='date'>16</var>, <var data-var='time'>13:14</var> UTC Resolved - The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy. Jul <var data-var='date'>15</var>, <var data-var='time'>23:33</var> UTC Investigating - Confluent is aware of the ongoing AWS incident affecting eu-central-1. We have identified degraded performance impacting clusters in this region, and our engineers are actively working with AWS to mitigate the issue.

Kafka cluster performance degradation for clusters in AWS region eu-central-1

Jul <var data-var='date'>16</var>, <var data-var='time'>03:21</var> UTC Resolved - Resolved. Apr <var data-var='date'> 2</var>, <var data-var='time'>15:40</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>19:52</var> 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. Mar <var data-var='date'>20</var>, <var data-var='time'>13:58</var> 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.

Elevated error rates in AWS me-south-1 and me-central-1 regions

Jul <var data-var='date'>13</var>, <var data-var='time'>16:04</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>13</var>, <var data-var='time'>14:36</var> UTC Monitoring - A fix has been implemented and we are monitoring the results Jul <var data-var='date'>13</var>, <var data-var='time'>14:25</var> UTC Identified - The issue has been identified and a fix is being implemented.

Confluent Cloud Metrics API is currently experiencing elevated latency and error rates.

Jun <var data-var='date'>29</var>, <var data-var='time'>20:36</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>29</var>, <var data-var='time'>17:44</var> UTC Identified - Kafka producers and consumers to some clusters in Azure spaincentral may not be able to produce and consume records from their topic partitions. An issue has been identified by Azure and is under investigation.

Kafka consumer and producer degradation in Azure spaincentral

Jun <var data-var='date'>29</var>, <var data-var='time'>12:50</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>29</var>, <var data-var='time'>12:10</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>29</var>, <var data-var='time'>12:04</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>29</var>, <var data-var='time'>11:40</var> UTC Investigating - We are currently investigating this issue.

Confluent Cloud Metrics API is currently experiencing elevated error rates

Jun <var data-var='date'>25</var>, <var data-var='time'>17:53</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>25</var>, <var data-var='time'>16:12</var> UTC Monitoring - Confluent Cloud Metrics API experienced increased error rates from 2026-06-25 15:15 UTC to 2026-06-25 15:55 UTC. The incident has been mitigated and the systems have recovered. We are continuing to monitor. Jun <var data-var='date'>25</var>, <var data-var='time'>15:59</var> UTC Investigating - We are currently investigating this issue.

Increased error rates in Metrics API

Jun <var data-var='date'>23</var>, <var data-var='time'>07:00</var> UTC Resolved - On June 23rd, between 7:00 to 7:16 UTC the Confluent Cloud Metrics API was unavailable. Confluent has identified the issue and restored functionality.

Confluent Cloud Metrics API unavailable

Jun <var data-var='date'>21</var>, <var data-var='time'>09:19</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>21</var>, <var data-var='time'>09:19</var> UTC Update - We are continuing to monitor for any further issues. Jun <var data-var='date'>21</var>, <var data-var='time'>08:31</var> UTC Monitoring - The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability. Jun <var data-var='date'>21</var>, <var data-var='time'>07:14</var> UTC Identified - The team has identified the root cause of the issues affecting standard and basic Kafka clusters in the AWS us-east-2 region. We are actively working on a mitigation strategy and will provide further updates as they become available.

Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2

Jun <var data-var='date'>16</var>, <var data-var='time'>17:58</var> UTC Resolved - No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC. Jun <var data-var='date'>16</var>, <var data-var='time'>17:58</var> UTC Update - No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC. Jun <var data-var='date'>16</var>, <var data-var='time'>16:43</var> UTC Monitoring - We have found the root cause and have mitigated the problem as of 2026-06-16 16:09 UTC. We will monitor for any residual issues before resolving this incident in 1 hour. Jun <var data-var='date'>16</var>, <var data-var='time'>16:02</var> UTC Investigating - We are currently experiencing Intermittent Produce/Consume Unavailability in Azure Dedicated clusters. The problem started at 2026-06-16 13:20 UTC. We are currently investigating and will update as we know more.

Intermittent Produce/Consume Unavailability in Azure Dedicated clusters

Jun <var data-var='date'>12</var>, <var data-var='time'>11:55</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>12</var>, <var data-var='time'>09:53</var> UTC Monitoring - We have deployed a mitigation for the intermittent inter-region connectivity issues affecting AWS us-west-2, which began at approximately 04:00 UTC. Customers with clusters in or communicating with this region may have experienced delays or errors with Cluster Linking, Flink processing, and accessing logs in the Confluent Cloud UI. We are monitoring to confirm full restoration. Jun <var data-var='date'>12</var>, <var data-var='time'>09:11</var> UTC Update - We continue to investigate intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking, Flink processing and logs for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation. Jun <var data-var='date'>12</var>, <var data-var='time'>07:42</var> UTC Investigating - We are investigating intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking and Apache Flink processing for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.

Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2

Jun <var data-var='date'>12</var>, <var data-var='time'>00:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>28</var>, <var data-var='time'>19:23</var> UTC Update - Let's Encrypt has addressed the problem they had previously identified with their cross-signed CA certificates (see https://community.letsencrypt.org/t/upcoming-let-s-encrypt-profile-changes-on-may-13/247049/4). Confluent is now resuming this maintenance operation to replace the intermediate certificates. No downtime is expected. We will provide updates as necessary. May <var data-var='date'>15</var>, <var data-var='time'>22:34</var> UTC Update - Let's Encrypt intermediate certificate rotation is delayed as announced by Let's Encrypt: https://community.letsencrypt.org/t/upcoming-let-s-encrypt-profile-changes-on-may-13/247049/4 May <var data-var='date'>13</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'> 1</var>, <var data-var='time'>16:51</var> 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 Mar <var data-var='date'>13</var>, <var data-var='time'>21:45</var> 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

Is Confluent down?

Confluent status is UP

Lastest published events

Missing Metrics on Confluent Cloud

Elevated error rates in Azure East US

Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

Confluent Services, Components and Regions

Recent Confluent events

Missing Metrics on Confluent Cloud

Elevated error rates in Azure East US

Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

Elevated error rates in Azure Germany West Central region

Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

Confluent Cloud Metrics API experienced elevated latency and error rates