Confluent had 53 outages in the last 2 years totaling 383h 31m of downtime — averaging 2.2 incidents per month.
There were 53 Confluent outages since June 24, 2025 totaling 383h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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
We are continuing to investigate this issue.
Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.
Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.
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.
Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.
We are currently investigating the root cause.
We are currently investigating the issue. In the meantime, customers can use the CLI to manage the resources.
This incident has been resolved.
We are experiencing provisioning delays in Azure eastus region.
We've identified a mitigation method and are rolling this out across affected networks.
Provisioning delays have been partially mitigated, but there may still be delays for eastus region.
Dedicated private networks and dedicated Kafka clusters provisioning with PrivateLink or VNet Peering are unavailable in the Azure eastus region.
This incident has been resolved.
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.
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.
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.
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.
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.
All impacted Flink compute pools have been fixed and degraded statements have recovered.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing delays in cluster provisioning in AWS. The team is currently investigating.
We have identified the root cause as a failure in the underlying disk-mounting mechanism, which has required manual intervention. The impacted nodes have been fixed, and we are preparing to roll out a permanent fix.
A fleet-wide deployment containing a permanent fix is underway. We are continuing to monitor the rollout and will update when it is complete.
The deployment is now complete and the AWS cluster provisioning delays have been mitigated as of 03:20 UTC on Oct 7, 2025. We will monitor for any residual issues before resolving this incident in 1 hour.
This incident has been resolved.
We are currently experiencing degraded performance in the provisioning flow for Schema Registry, KSQL, and Stream Governance resources. Impact: Newly created clusters and API keys for these services may be delayed. You may also encounter authentication/authorization errors when using newly created keys. Unaffected: Existing clusters, keys, and resources continue to function as expected. Our engineering team is actively investigating and working to restore normal provisioning times. We will provide updates as more information becomes available.
Provisioning Performance Restored Provisioning times for Schema Registry, KSQL, and Stream Governance resources have returned to normal. Our engineering team is continuing to investigate the root cause to ensure long-term stability.
Provisioning times have returned to normal since the last update and a mitigation has been put in place to prevent further regressions. Confluent will continue to monitoring to ensure that the issues have been resolved.
This incident has been fully resolved.
Confluent is currently experiencing a networking issue in the AWS us-east-1 region that is affecting service operations. Our team has identified the root cause and is actively working on mitigation to restore full service. We will provide updates as progress continues.
The root cause has been identified and our team is actively working on mitigation to restore full service
Our team continues to actively work on mitigating the networking issue in AWS us-east-1. Progress is being made toward restoring full service.
We continue to work on mitigation while some operations have been restored in AWS us-east-1.
As of 13:19 UTC on October 1st, 2025, this incident has been mitigated. We'll continue monitoring but no longer expect any customer impact.
This incident has been resolved.
As of 23:54 UTC on 26 Sep 2025, customers with clusters in the Azure Switzerland North region may experience downtime due to an Azure region outage. Confluent engineering has been engaged and is investigating the issue.
As of 23:54 UTC on 26 Sep 2025, customers with clusters in the Azure Switzerland North region may experience service unavailability or degraded performance due to an Azure region outage. Azure has identified a networking issue and are preparing a hotfix.
Starting at 23:54 UTC on 26 September 2025, customers in Switzerland North may experience service unavailability or degraded performances for resources hosted in the region. Virtual Machines may have shutdown to preserve data integrity. We were alerted to this issue by our telemetry informing us in a significant drop in traffic. It was discovered that a recent deployment introduced a malformed prefix in one of the certificates used for connection authorization. We have pinpointed the deployment error involving the certificate prefix and are rolling back the faulty deployment to restore normal traffic flow and service availability. Majority of the impacted services have been fully recovered, and a subset are nearing completion. We continue to monitor traffic and service stability to ensure full recovery.
Starting 23:54 UTC on 26 Sep 2025, customers with clusters in the Azure Switzerland North region may experience service unavailability or degraded performance due to an Azure region outage. Azure has fixed the issue and we are working to recover all affected services. The majority of impacted services have been fully recovered, and a subset are nearing completion. We continue to monitor traffic and service stability to ensure full recovery.
All services in the Azure Switzerland North region have now been fully recovered.
As of September 24, 2025 customers may observe that their AWS Transit Gateway connection is in a Failed state from within the Confluent Cloud UI. But connectivity is unaffected. Engineering has been engaged and are investigating the issue.
As of September 24, 2025, some customers may see their AWS Transit Gateway connection displayed as Failed in the Confluent Cloud UI. Connectivity is not impacted, and traffic is flowing normally. Our engineering team is actively investigating.
As of September 25, 2025, customers may observe that their AWS Transit Gateway connection is in a Failed state from within the Confluent Cloud UI. However this shouldn't impact any of your services or connectivity. From our assessment this is likely a problem from AWS and we have escalated to AWS for resolution.
AWS has confirmed that when an external principal is removed from a customer's resource share, Confluent cannot determine if the TGW attachment still exists. This results in the AWS Transit Gateway connection displaying in the Failed state from within the Confluent Cloud UI. Affected users should validate the TGW resource share is in place per our documentation (https://docs.confluent.io/cloud/current/networking/aws-transit-gateway.html#add-an-aws-transit-gateway-attachment-in-ccloud).
We experienced issues related to our identity service which has impacted all confluent cloud management APIs. This resulted in an outage on our UI, API, CLI and Terraform interfaces. We have mitigated the issue and are now monitoring the APIs to ensure they are stable.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are experiencing issues related to internal topic compaction causing topic size to grow. This is impacting cluster performance in a limited number of clusters with extreme cases. We have identified the root cause and are actively working on a fix. Next update soon.
Mitigation is still in progress. Next update in 3 hours
Mitigation is in progress. Next update in 2 hours.
We have deployed mitigation steps. We'll continue monitoring but no longer expect any customer impact.
Issues related to internal topic compaction have been resolved.
This incident has been resolved.
We are experiencing delays in our data pipeline which is impacting KSQL and Schema Registry cluster creation in all regions and cloud providers. We are currently investigating the issue and will post an update in the next 30 minutes.
We have deployed mitigation steps and the delays have improved. We'll continue monitoring but no longer expect any customer impact.
This incident has been resolved.
Starting at 08:00 UTC on August 18, 2025, some customers who have created or updated role based access control policies during this incident may see a delay in those new rules getting applied. Additionally, customers who have configured OAUTH where their public key is set to be refreshed during this incident may see additional authentication failures. This can impact clusters in any cluster regardless of region or cloud provider. We are currently investigating the issue. We will post an update in 30 minutes.
We are continuing to investigate. The potential impact also includes customer who have configured OAUTH and have changed their public key in any way, including refreshing it or creating a new public key during this incident. We will post an update in 60 minutes, or sooner if mitigation has been achieved.
As of 19:38 UTC on August 18, 2025, this incident has been mitigated. We'll continue monitoring but no longer expect any customer impact.
This incident has been resolved.
This manifests itself as networking errors on affected clusters. We are currently investigating and attempting to mitigate or provide a work-around.
Affected resources are limited to a single zone in GCP, us-central1-a. We are continuing to investigate.
GCP has confirmed that starting, August 6th 12:46 PM UTC, us-central1 is experiencing packet loss causing elevated latency and errors. GCP have communicated that they will provide an update shortly
Resources in multiple zones in GCP us-central1 are affected. We are continuing to investigate
Many clusters in the affected region are recovering. We are continuing to monitor.
We are seeing mitigation for all impacted Kafka clusters in GCP us-central1 and are continuing to monitor.
This incident has been resolved.
This issue started on July 23rd, 2025 08:00 UTC, and has been mitigated as of July 23rd, 2025 15:17 UTC. At this time, we have deployed a fix for the issue and are monitoring to see recovery.
We have verified that the fix rolled out works as expected and no longer see errors. All historical queries with longer time ranges should work as normal.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
Confluent is observing similar symptoms to the earlier issue: https://status.confluent.cloud/incidents/c4nvjkxz5vqc Investigation and mitigation efforts are underway.
We applied a mitigation that has bought the Flink service to a healthy status and are currently monitoring the service.
This incident has been resolved.
We are currently investigating the issue and attempting to mitigate or provide a work-around.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
The issue has been fixed, Flink statements are running as expected and new statements can be submitted. Ongoing Monitoring.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and the mitigation steps are being executed.
The issue has been mitigated and Confluent is continuing to monitor the health of Freight brokers in AWS ap-south1 region.
This incident is resolved.
Starting Jul 7, approximately 17:39 UTC, Flink APIs to fetch regions and compute pools encountered failures. The issue was mitigated approximately Jul 7, 18:25 UTC and Confluent is actively monitoring the status.
The incident has been resolved and APIs are functioning correctly.
Between 02:00 UTC and 02:05 UTC some customers running clusters in AWS ME-SOUTH-1 may have experienced increased errors or slowness of their producer and consumers. This issue was detected and auto-mitigated.