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

New Intermediate TLS Certificates rollout starting May 13th, 2026

Jun <var data-var='date'> 4</var>, <var data-var='time'>16:47</var> UTC Resolved - The incident has been resolved and us-east-1 (use1-az4) is fully operational. May <var data-var='date'>12</var>, <var data-var='time'>18:51</var> UTC 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 <var data-var='date'> 9</var>, <var data-var='time'>13:19</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>01:55</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>01:14</var> 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.

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

May <var data-var='date'>29</var>, <var data-var='time'>21:47</var> UTC Resolved - The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally. May <var data-var='date'>29</var>, <var data-var='time'>16:49</var> UTC Update - Confluent services in the Azure West US2 region are now healthy. We are continuing to monitor for residual effects as Azure continues to address their service outage. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status May <var data-var='date'>29</var>, <var data-var='time'>10:25</var> UTC Monitoring - We are monitoring the health of impacted Confluent services in the Azure West US2 region. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status May <var data-var='date'>29</var>, <var data-var='time'>06:47</var> UTC Update - Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation. May <var data-var='date'>29</var>, <var data-var='time'>05:57</var> UTC Investigating - We are currently experiencing increased error rates and latencies in the Azure westus2 region. This began at approximately 5:10 AM UTC 29th May. Our team is actively investigating it.

Elevated error rates and latencies in Azure westus2 region

May <var data-var='date'>22</var>, <var data-var='time'>00:22</var> UTC Resolved - The incident has been resolved. May <var data-var='date'>22</var>, <var data-var='time'>00:21</var> 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.

Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2

May <var data-var='date'> 7</var>, <var data-var='time'>03:08</var> UTC Resolved - The maintenance is complete. May <var data-var='date'> 6</var>, <var data-var='time'>22:12</var> 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.

Scheduled Confluent Cloud maintenance on May 6, 2026

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

Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

Apr <var data-var='date'>21</var>, <var data-var='time'>09:49</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>21</var>, <var data-var='time'>09:34</var> UTC Monitoring - We are experiencing delays Tableflow external catalog sync in AWS. Our team has added a fix to resolve the situation and are monitoring the same.

Experiencing delays in Tableflow external catalog syncs in AWS

Mar <var data-var='date'>20</var>, <var data-var='time'>00:55</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 3</var>, <var data-var='time'>05:34</var> UTC Update - 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 <var data-var='date'> 2</var>, <var data-var='time'>15:37</var> UTC Update - Confluent Cloud services in AWS me-south-1 remain stable and operating normally following mitigation. We continue to monitor for any residual issues. Confluent Cloud services in AWS me-central-1 continue to experience a complete outage due to the ongoing AWS regional infrastructure failure in that region. Mar <var data-var='date'> 2</var>, <var data-var='time'>10:35</var> UTC Monitoring - Confluent cloud services in AWS me-south-1 are mitigated. They are currently being monitored. Confluent Cloud Services in AWS me-central-1 are still disrupted owing to regional outage at AWS. Mar <var data-var='date'> 2</var>, <var data-var='time'>08:32</var> UTC Update - Confluent Cloud services in AWS me-central-1 region are experiencing a major outage. They are linked to AWS's me-central-1 regional outage Confluent Cloud services in AWS me-south-1 are being mitigated. Mar <var data-var='date'> 2</var>, <var data-var='time'>07:19</var> UTC Investigating - We are experiencing increased error rates in some of our Confluent Cloud services in AWS me-south-1 and me-central-1 regions. This began at approximately 05:00 AM UTC today and is linked to disruptions in AWS’s availability zones in these regions (mec1-az1, mec1-az3 and mes1-az2). Team is currently working on mitigating these and will provide updates as the situation evolves.

Mar <var data-var='date'> 5</var>, <var data-var='time'>07:22</var> UTC Resolved - Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal. Mar <var data-var='date'> 5</var>, <var data-var='time'>04:40</var> UTC Monitoring - Confluent Cloud Metrics API was unavailable from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC, the incident has been mitigated and the systems are functioning well. We are continuing to monitor and will provide an update on or before 2026-03-05 06:40 UTC.

Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC

Mar <var data-var='date'> 1</var>, <var data-var='time'>22:05</var> UTC Resolved - This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region. Mar <var data-var='date'> 1</var>, <var data-var='time'>21:41</var> UTC Monitoring - The problem has been mitigated as of 21:15 PM UTC today. All Confluent Cloud services are now healthy in me-central-1 region and we will monitor for any residual issues before resolving this incident in 1 hour. Mar <var data-var='date'> 1</var>, <var data-var='time'>18:48</var> UTC Identified - We have identified the cause of the problem to be disruption in one of AWS’s availability zones (mec1-az2). We are taking steps to confirm the safest path to mitigation for any impacted Confluent Cloud services in this region. Mar <var data-var='date'> 1</var>, <var data-var='time'>18:08</var> UTC Investigating - We are experiencing increased error rates in some of our Confluent Cloud services in the AWS me-central-1 region. This began at approximately 12:51 PM UTC today and is linked to a disruption in one of AWS’s availability zones (mec1-az2). Our team is actively applying mitigation steps and will provide updates as the situation evolves.

Elevated Error Rates in AWS me-central-1 region

Feb <var data-var='date'>27</var>, <var data-var='time'>18:16</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>27</var>, <var data-var='time'>03:25</var> UTC Update - We are continuing to monitor for any further issues. Feb <var data-var='date'>26</var>, <var data-var='time'>17:41</var> UTC Monitoring - A fix has been implemented and we are monitoring the results Feb <var data-var='date'>26</var>, <var data-var='time'>01:11</var> UTC Update - At this time, single zone clusters in us-south1 Zone-a are impacted. Feb <var data-var='date'>25</var>, <var data-var='time'>12:02</var> UTC Identified - GCP has identified the issue and is actively working on applying mitigation. Feb <var data-var='date'>25</var>, <var data-var='time'>05:01</var> UTC Investigating - We are currently investigating the issue

Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates

Feb <var data-var='date'>27</var>, <var data-var='time'>01:57</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>26</var>, <var data-var='time'>23:07</var> UTC Identified - The issue has been identified and a fix is being implemented. Feb <var data-var='date'>26</var>, <var data-var='time'>19:56</var> UTC Investigating - Azure is investigating the issue and we will post an update soon.

All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing

Feb <var data-var='date'>26</var>, <var data-var='time'>22:24</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>26</var>, <var data-var='time'>22:23</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>26</var>, <var data-var='time'>13:59</var> UTC Investigating - Provisioning new networks in this region can potentially fail. We are investigating the issue and will post an update soon.

Is Confluent down?

Confluent status is UP

Lastest published events

Elevated error rates and latency in GCP us-west1

Flink statements degraded in GCP us-central1 region

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

Confluent Services, Components and Regions

Recent Confluent events

Elevated error rates and latency in GCP us-west1

Flink statements degraded in GCP us-central1 region

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

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

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

Kafka consumer and producer degradation in Azure spaincentral