THIS IS A SCHEDULED EVENT May <var data-var='date'>13</var>, <var data-var='time'>00:00</var> UTC &nbsp;-&nbsp; Jun <var data-var='date'>12</var>, <var data-var='time'>00:00</var> UTCApr <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-2026Mar <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

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

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 resultsFeb <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.

Network provisioning service in Azure East US region is degraded

Feb <var data-var='date'>25</var>, <var data-var='time'>01:07</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>25</var>, <var data-var='time'>00:33</var> UTC Identified - Issue has been identified and we are currently deploying the fix.Feb <var data-var='date'>24</var>, <var data-var='time'>21:16</var> UTC Update - We are continuing to investigate this issue.Feb <var data-var='date'>24</var>, <var data-var='time'>21:16</var> UTC Update - We are currently working on a mitigation.Feb <var data-var='date'>24</var>, <var data-var='time'>21:15</var> UTC Investigating - We are experiencing an elevated level of Kafka REST API Errors with error code 429 in AWS us-west-2 and are currently looking into the issue. This issue impacts Kafka eSKU clusters in this regions.

Elevated Kafka REST API Errors in AWS us-west-2

Feb <var data-var='date'>24</var>, <var data-var='time'>09:58</var> UTC Resolved - The issue was resolved successfully. All systems working as expected.Feb <var data-var='date'>24</var>, <var data-var='time'>07:27</var> UTC Monitoring - GCP has identified the root cause and has fixed the same. Currently monitoring.Feb <var data-var='date'>24</var>, <var data-var='time'>00:23</var> UTC Update - We are continuing to investigate this issue with GCP. GCP is actively working on applying mitigation.Feb <var data-var='date'>23</var>, <var data-var='time'>22:18</var> UTC Update - We are continuing to investigate this issue.Feb <var data-var='date'>23</var>, <var data-var='time'>22:17</var> UTC Update - Starting 2/21/2026, 21:00 UTC We are observing Elevated Kafka Latency in GCP asia-southeast1 region for less than 0.1% of produce and fetch requests for some customers. Median latencies for both produce and fetch requests are not impacted. We are actively working with GCP to identify the root cause of the issue. We will provide next update in 2 hours or earlier.Feb <var data-var='date'>23</var>, <var data-var='time'>22:12</var> UTC Investigating - We are currently investigating this issue.

Elevated Kafka Latency in GCP asia-southeast1

Feb <var data-var='date'>12</var>, <var data-var='time'>02:45</var> UTC Resolved - The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.Feb <var data-var='date'>12</var>, <var data-var='time'>01:58</var> UTC Update - We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.Feb <var data-var='date'>12</var>, <var data-var='time'>00:07</var> UTC Identified - The issue has been identified with Azure support and working on mitigating failed cluster creations. We will provide another update in the next 90 minutes or sooner if mitigation has been achieved.Feb <var data-var='date'>11</var>, <var data-var='time'>22:50</var> UTC Update - We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.Feb <var data-var='date'>11</var>, <var data-var='time'>22:14</var> UTC Investigating - Confluent has been experiencing failures creating all new clusters in Azure westus3, southcentralus, and eastus2. The impact started at 09:50 UTC on Wednesday, February 11, 2026. We are investigating and will provide another update in 30 minutes or sooner if mitigation has been achieved.

All new cluster creations in Azure westus3, southcentralus, and eastus2 are failing

Feb <var data-var='date'> 4</var>, <var data-var='time'>00:48</var> UTC Resolved - The issue has been resolved and services are operating normally. The root cause was a networking configuration change in the us-west-2 region that caused client connection issues starting at approximately 21:33 UTC, resulting in intermittent service disruption across several Confluent Cloud services, including Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication. The change was reverted, and as of 00:20 UTC, services have been fully restored.Feb <var data-var='date'> 4</var>, <var data-var='time'>00:08</var> UTC Monitoring - Confluent has identified the cause of the issue and reverted the related configuration change. During the incident, some Kafka clusters experienced intermittent connectivity issues, and some control plane services, including metrics, logging, authentication, and new cluster provisioning, were briefly impacted. The issue has been mitigated, services are stable, and we continue to monitor.Feb <var data-var='date'> 3</var>, <var data-var='time'>23:25</var> UTC Identified - We’ve identified the cause of the connection issues and are reverting a recent configuration change. Service stability is improving as the rollback progresses. We’ll continue monitoring and provide an update once all services are confirmed restored.Feb <var data-var='date'> 3</var>, <var data-var='time'>21:33</var> UTC Investigating - We are currently investigating this issue.

Confluent Cloud Service Outage

Jan <var data-var='date'> 8</var>, <var data-var='time'>16:25</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'> 8</var>, <var data-var='time'>13:09</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Jan <var data-var='date'> 8</var>, <var data-var='time'>12:30</var> UTC Investigating - We are currently investigating this issue.

Multiple customers are reporting networking instability in the Azure West Europe region

Dec <var data-var='date'>16</var>, <var data-var='time'>06:00</var> UTC Resolved - Metrics API /export endpoint was emitting 400 errors from 06:02 UTC to 10:20 UTC

Metrics API /export endpoint emitting 400 errors

Dec <var data-var='date'>10</var>, <var data-var='time'>04:48</var> UTC Resolved - This issue has been resolved.Dec <var data-var='date'> 9</var>, <var data-var='time'>14:51</var> UTC Monitoring - Normal metrics operations have been restored for all originally affected clusters. We are actively monitoring for any new occurrences of the issue.Dec <var data-var='date'> 9</var>, <var data-var='time'>01:13</var> UTC Identified - The mitigation is nearing completion and we have seen recovery on most clusters. The root cause has been identified.Dec <var data-var='date'> 8</var>, <var data-var='time'>20:44</var> UTC Update - We are mitigating the impacted clusters and continuing to investigate the root cause.Dec <var data-var='date'> 8</var>, <var data-var='time'>17:48</var> UTC Investigating - We are investigating an issue with missing metrics affecting a small number of Confluent Cloud Kafka clusters.

Missing metrics in some Confluent Cloud Kafka clusters

Dec <var data-var='date'> 3</var>, <var data-var='time'>02:04</var> UTC Resolved - No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.Dec <var data-var='date'> 3</var>, <var data-var='time'>01:32</var> UTC Monitoring - A fix has been applied to all regions and we've seen recovery in all affected regions. We'll continue to monitor for the next 30 minutes.Dec <var data-var='date'> 2</var>, <var data-var='time'>23:14</var> UTC Update - The team has successfully applied a fix to asia-northeast1 and we're seeing recovery there. Meanwhile the team is applying mitigations in the other affected regions.Dec <var data-var='date'> 2</var>, <var data-var='time'>22:03</var> UTC Identified - The root cause for the issue has been identified and the team is working on applying a mitigation.Dec <var data-var='date'> 2</var>, <var data-var='time'>21:37</var> UTC Investigating - This manifests itself in new Flink jobs remaining stuck in "Statement Status: Pending", existing Flink jobs being requested to stop remaining stuck in "Statement Status: Stopping". This issue started manifesting at 2025-12-02 19:53 UTC. We are currently investigating the issue and attempting to mitigate or provide a work-around.

Flink job submission and job scale operations are affected in GCP asia-northeast1, europe-west8, europe-north1, southamerica-east1

Nov <var data-var='date'>28</var>, <var data-var='time'>18:33</var> UTC Resolved - This incident has been resolved.Nov <var data-var='date'>28</var>, <var data-var='time'>18:02</var> UTC Update - We have fixed the issue, and are now monitoring the few affected tables to ensure they all return to full operation. As of Nov 28th 6:00PM UTC customers should see normal operations with Confluent systems.Nov <var data-var='date'>28</var>, <var data-var='time'>13:25</var> UTC Identified - We've identified the issue; a hotfix is on its way to production.

BYOK-enabled Tableflow deployments may experience data inconsistencies when executing queries that include filter predicates

Nov <var data-var='date'>21</var>, <var data-var='time'>01:00</var> UTC Resolved - Some of the Freight customers in AWS us-east-1 could have experienced latency spikes intermittently

Confluent Cloud Freight customers experiencing latency spikes intermittently in us-east-1

Nov <var data-var='date'>17</var>, <var data-var='time'>21:07</var> UTC Resolved - This issue has been resolved, and there should be no further log loss. All subsequent connector log events are now accessible.Nov <var data-var='date'>17</var>, <var data-var='time'>19:53</var> UTC Monitoring - A fix has been implemented, ensuring no further log loss. All subsequent connector log events are now available, and we will continue monitoring the results.Nov <var data-var='date'>17</var>, <var data-var='time'>15:29</var> UTC Identified - We have identified the cause of the issue and have begun mitigation steps. Our investigation confirmed that some connector log events were lost as a result of this issue. The mitigation currently in progress will prevent further log loss, but we will be unable to recover the events that were previously lost. The full mitigation is expected to take up to 8 hours to complete for all clusters. We will provide a further update within the next 2 hours.Nov <var data-var='date'>17</var>, <var data-var='time'>14:38</var> UTC Update - We are continuing to investigate this issue.Nov <var data-var='date'>17</var>, <var data-var='time'>14:28</var> UTC Investigating - We are experiencing issues with the availability of recent Connector event logs across all regions and cluster types. The problem started at 09:00 UTC on November 17, 2025. We are currently investigating, and will update as we know more.

Confluent Cloud Connector event logs - Unavailable - All clusters - All regions

Nov <var data-var='date'> 6</var>, <var data-var='time'>21:39</var> UTC Resolved - All affected clusters are now fully operational.Nov <var data-var='date'> 6</var>, <var data-var='time'>14:03</var> UTC Monitoring - Issues observed with Azure Europe West are now resolved. Most impacted services have recovered and are operational. We are working on resolving issues impacting performance for few customers.Nov <var data-var='date'> 6</var>, <var data-var='time'>01:48</var> UTC Update - We are monitoring Azure updates and recovery closely. We are noticing partial recovery in a subset of affected resources and will provide an update as more information becomes available.Nov <var data-var='date'> 5</var>, <var data-var='time'>22:29</var> UTC Update - Azure has provided an update on it's Status Page (https://azure.status.microsoft/en-us/status) stating that recovery efforts are in progress. We will provide an update within 60 minutes.Nov <var data-var='date'> 5</var>, <var data-var='time'>21:13</var> UTC Update - Azure posted outage details on its status page: https://azure.status.microsoft/en-us/status. No material changes since last update. We continue monitoring the situation from our side and will provide the next update within 60 minutes or when the status changes.Nov <var data-var='date'> 5</var>, <var data-var='time'>19:51</var> UTC Identified - The issue was localized to a single Availability Zone in Azure West Europe region. Only Single Zone Kafka Clusters are affected at this time. Multi-Zone clusters experienced intermittent availability and elevated latency for produce and fetch requests but auto-recovered within minutes. We are continuing to work with Microsoft Azure for resolution of affected single zone clusters. We will post next update by 1:00 PST.Nov <var data-var='date'> 5</var>, <var data-var='time'>19:22</var> UTC Update - We are continuing to investigate this issue.Nov <var data-var='date'> 5</var>, <var data-var='time'>18:47</var> UTC Update - We are beginning to see some recovery of the affected Kafka clusters.Nov <var data-var='date'> 5</var>, <var data-var='time'>18:19</var> UTC Investigating - We are currently experiencing an issue that appears to be related to an ongoing incident with Microsoft Azure. We are actively working with the Azure team to confirm the impact and will provide updates as soon as more information becomes available.

Availability issues for Kafka clusters in Azure West Europe

Oct <var data-var='date'>30</var>, <var data-var='time'>00:42</var> UTC Resolved - Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.Oct <var data-var='date'>29</var>, <var data-var='time'>20:35</var> UTC Update - Flink statements in Azure have recovered following Microsoft’s rollback of a recent network configuration change. Confluent systems are fully operational at this time, though Microsoft is continuing to monitor the rollback and validate stability. We will remain in monitoring until Microsoft confirms full recovery.Oct <var data-var='date'>29</var>, <var data-var='time'>18:59</var> UTC Monitoring - Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.Oct <var data-var='date'>29</var>, <var data-var='time'>18:39</var> UTC Identified - Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.Oct <var data-var='date'>29</var>, <var data-var='time'>18:12</var> UTC Update - We are continuing to investigate this issue.Oct <var data-var='date'>29</var>, <var data-var='time'>16:55</var> UTC Investigating - Confluent engineers are engaged on the incident. The impact is related to the ongoing Azure incident. You can find more information here: https://azure.status.microsoft/en-us/status

Degraded Flink statements in Azure

Oct <var data-var='date'>29</var>, <var data-var='time'>17:00</var> UTC Resolved - Some customers in AWS us-east-1 may have experienced unavailability of produce requests for Enterprise SKU clusters from 3:40 to 4:05 PM UTC.

Brief unavailability of produce requests for Enterprise SKU clusters in AWS us-east-1

Oct <var data-var='date'>27</var>, <var data-var='time'>18:13</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'>27</var>, <var data-var='time'>17:56</var> UTC Update - We are currently investigating the issue. In the meantime, customers can use the CLI to manage the resources.Oct <var data-var='date'>27</var>, <var data-var='time'>17:48</var> UTC Investigating - We are currently investigating the root cause.

Customers are encountering a 404 error when attempting to access resources within the Confluent Cloud UI.

Oct <var data-var='date'>25</var>, <var data-var='time'>05:14</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'>24</var>, <var data-var='time'>17:05</var> UTC Update - Dedicated private networks and dedicated Kafka clusters provisioning with PrivateLink or VNet Peering are unavailable in the Azure eastus region.Oct <var data-var='date'>23</var>, <var data-var='time'>23:56</var> UTC Update - Provisioning delays have been partially mitigated, but there may still be delays for eastus region.Oct <var data-var='date'>23</var>, <var data-var='time'>20:17</var> UTC Update - We've identified a mitigation method and are rolling this out across affected networks.Oct <var data-var='date'>22</var>, <var data-var='time'>22:38</var> UTC Identified - We are experiencing provisioning delays in Azure eastus region.

Delayed cluster provisioning in Azure eastus region

Oct <var data-var='date'>22</var>, <var data-var='time'>22:45</var> UTC Resolved - All impacted Flink compute pools have been fixed and degraded statements have recovered.Oct <var data-var='date'>22</var>, <var data-var='time'>22:25</var> UTC Monitoring - All impacted Flink compute pools have been fixed and degraded statements have now recovered. We are continuing to monitor to ensure no further issues occur.Oct <var data-var='date'>22</var>, <var data-var='time'>20:33</var> UTC Update - A fix has been applied to a number Flink compute pools, but some customers may still see failing statement failures. We are continuing to apply the fixes to the remaining impacted pools. The next update will be posted in 1 hour, or sooner if mitigation has been completed.Oct <var data-var='date'>22</var>, <var data-var='time'>19:04</var> UTC Update - We are continuing to mitigate Flink statement failures and apply fixes to necessary compute pools. We will post an update in 1 hour, or sooner if mitigation has been completed.Oct <var data-var='date'>22</var>, <var data-var='time'>17:42</var> UTC Identified - The issue causing Flink statement failures has been identified and a hotfix has been prepared. We are actively working to mitigate all impacted compute pools.Oct <var data-var='date'>22</var>, <var data-var='time'>16:21</var> UTC Investigating - Flink statements are failing to execute across multiple regions. The impact started at 15:12 UTC on Oct. 22, 2025. Customers may be experiencing increased rate of degraded statements and internal errors. We are currently investigating the issue.

Is Confluent down?

Confluent status is PARTIAL OUTAGE

Components with issues

Lastest published events

New Intermediate TLS Certificates rollout starting May 13th, 2026

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

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

Confluent Services, Components and Regions

Recent Confluent events

New Intermediate TLS Certificates rollout starting May 13th, 2026

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

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

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

Elevated Error Rates in AWS me-central-1 region

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

Get your FREE account now,
5 monitors included!

Is Confluent down?

Confluent status is PARTIAL OUTAGE

Components with issues

Lastest published events

New Intermediate TLS Certificates rollout starting May 13th, 2026

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

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

Confluent Services, Components and Regions

Recent Confluent events

New Intermediate TLS Certificates rollout starting May 13th, 2026

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

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

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

Elevated Error Rates in AWS me-central-1 region

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

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!