Confluent Outage History

Started Oct 20, 2026, 08:02 AM UTC· resolved Oct 20, 2026, 06:27 PM UTC

1. investigating Oct 20, 2026, 08:02 AM UTC

   Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2

2. investigating Oct 20, 2026, 12:55 PM UTC

   We are currently working to restore the impacted services. Most customers should be able to use Confluent Cloud services normally.

3. monitoring Oct 20, 2026, 02:46 PM UTC

   The underlying GCP issue has been mitigated. Confluent Cloud Kafka clusters in the affected zone are fully operational and Connect and Flink workloads have recovered. We are monitoring to confirm stability and working to restore the few remaining impacted resources.

4. monitoring Oct 20, 2026, 02:51 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 20, 2026, 06:27 PM UTC

   This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.

Read the full incident report →

Started Oct 16, 2026, 01:04 AM UTC· resolved Oct 16, 2026, 08:23 AM UTC

1. investigating Oct 16, 2026, 01:04 AM UTC

   We are investigating an issue that is causing delays in Kafka cluster provisioning in all regions. Existing clusters are not affected and continue to operate normally. We will provide another update within 60 minutes.

2. investigating Oct 16, 2026, 02:26 AM UTC

   We are still investigating the delays in Kafka cluster provisioning in all regions and are actively working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 3:30 UTC or as more information becomes available.

3. identified Oct 16, 2026, 03:34 AM UTC

   We have identified the cause of the delays in Kafka cluster provisioning in all regions and are working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 4:30 UTC or as more information becomes available.

4. identified Oct 16, 2026, 04:34 AM UTC

   We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available

5. identified Oct 16, 2026, 04:35 AM UTC

   We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available

6. identified Oct 16, 2026, 05:30 AM UTC

   We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Clusters provisioned during this window may take longer than usual to become available. Our next update will be posted by 6:30 UTC or as more information becomes available

7. monitoring Oct 16, 2026, 06:47 AM UTC

   We have mitigated the issue that was causing delays in Kafka cluster provisioning and we are now monitoring the health of new cluster provisioning. Existing clusters were not affected. We will post our next update by 07:30 UTC, or sooner if there is new information

8. monitoring Oct 16, 2026, 07:02 AM UTC

   We are continuing to monitor for any further issues.

9. resolved Oct 16, 2026, 08:23 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 15, 2026, 04:01 PM UTC· resolved Oct 15, 2026, 06:46 PM UTC

1. monitoring Oct 15, 2026, 04:01 PM UTC

   Between 14:23 and 15:35 UTC on Oct 15, 2026, some users of the Confluent Cloud Console experienced errors and degraded page functionality. No other services were affected. The issue has been mitigated and no further problems have been observed. Confluent is investigating root cause and monitoring. No customer action is required.

2. resolved Oct 15, 2026, 06:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2026, 11:27 PM UTC· resolved Oct 10, 2026, 12:23 AM UTC

1. investigating Oct 09, 2026, 11:27 PM UTC

   We are investigating an incident affecting services in the AWS us-east-1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates.

2. monitoring Oct 09, 2026, 11:43 PM UTC

   The observed elevated error rates seen in AWS us-east-1 have subsided and all services have recovered. No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider.

3. resolved Oct 10, 2026, 12:23 AM UTC

   This incident has been resolved. All affected services have fully recovered.

Read the full incident report →

Started Oct 09, 2026, 01:34 PM UTC· resolved Oct 10, 2026, 09:36 AM UTC

1. investigating Oct 09, 2026, 01:34 PM UTC

   Users in West Europe region of Azure could face elevated error rates and experience degraded performance. We are currently investigating the issue and attempting to mitigate or provide a work-around.

2. identified Oct 09, 2026, 04:46 PM UTC

   Azure has identified the issue and recovery actions are underway

3. identified Oct 09, 2026, 07:10 PM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 20:00 UTC, or sooner, as updates are available.

4. identified Oct 09, 2026, 08:02 PM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 21:00 UTC, or sooner, as updates are available.

5. identified Oct 09, 2026, 09:07 PM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 22:00 UTC, or sooner, as updates are available.

6. identified Oct 09, 2026, 10:04 PM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 23:00 UTC, or sooner, as updates are available.

7. identified Oct 09, 2026, 11:03 PM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 00:00 UTC, or sooner, as updates are available.

8. identified Oct 10, 2026, 12:12 AM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 01:00 UTC, or sooner, as updates are available.

9. identified Oct 10, 2026, 02:12 AM UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 03:00 UTC, or sooner, as updates are available.

10. identified Oct 10, 2026, 04:15 AM UTC

    Confluent continues to work closely with Azure, and we are seeing recovery across a number of affected clusters. Azure has not yet provided a specific ETA for full resolution. We will continue to provide updates as more information becomes available.

11. monitoring Oct 10, 2026, 08:47 AM UTC

    A fix has been implemented and we are monitoring the results.

12. resolved Oct 10, 2026, 09:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 08, 2026, 11:00 AM UTC· resolved Oct 08, 2026, 11:56 AM UTC

1. investigating Oct 08, 2026, 11:00 AM UTC

   Users in Germany West Central region of Azure could face elevated error rates. We are currently investigating the issue and attempting to mitigate or provide a work-around.

2. monitoring Oct 08, 2026, 11:38 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 08, 2026, 11:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 27, 2026, 12:33 AM UTC· resolved Sep 27, 2026, 02:15 AM UTC

1. resolved Sep 27, 2026, 02:00 AM UTC

   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.

Read the full incident report →

Started Sep 26, 2026, 06:40 AM UTC· resolved Sep 26, 2026, 07:43 PM UTC

1. investigating Sep 26, 2026, 06:40 AM UTC

   We are currently investigating an issue related to elevated error rates in Azure East US

2. identified Sep 26, 2026, 08:00 AM UTC

   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.

3. identified Sep 26, 2026, 01:23 PM UTC

   Systems are continuing to recover and are being monitored

4. identified Sep 26, 2026, 07:43 PM UTC

   We are continuing to work on a fix for this issue.

5. resolved Sep 26, 2026, 07:43 PM UTC

   This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.

Read the full incident report →

Started Sep 23, 2026, 11:47 AM UTC· resolved Sep 23, 2026, 11:17 PM UTC

1. identified Sep 23, 2026, 11:47 AM UTC

   The issue has been identified and a fix is being implemented.

2. identified Sep 23, 2026, 02:18 PM UTC

   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

3. monitoring Sep 23, 2026, 03:57 PM UTC

   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.

4. resolved Sep 23, 2026, 11:17 PM UTC

   This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.

Read the full incident report →

Started Sep 22, 2026, 03:09 PM UTC· resolved Sep 22, 2026, 07:58 PM UTC

1. investigating Sep 22, 2026, 03:09 PM UTC

   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.

2. monitoring Sep 22, 2026, 07:35 PM UTC

   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.

3. resolved Sep 22, 2026, 07:58 PM UTC

   This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.

Read the full incident report →

Started Sep 21, 2026, 04:04 PM UTC· resolved Sep 22, 2026, 01:31 AM UTC

1. investigating Sep 21, 2026, 04:04 PM UTC

   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.

2. investigating Sep 21, 2026, 04:15 PM UTC

   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.

3. investigating Sep 21, 2026, 04:32 PM UTC

   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.

4. investigating Sep 21, 2026, 05:04 PM UTC

   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.

5. investigating Sep 21, 2026, 06:01 PM UTC

   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.

6. investigating Sep 21, 2026, 06:31 PM UTC

   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.

7. investigating Sep 21, 2026, 07:08 PM UTC

   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.

8. investigating Sep 21, 2026, 07:33 PM UTC

   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.

9. investigating Sep 21, 2026, 08:03 PM UTC

   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.

10. identified Sep 21, 2026, 08:56 PM UTC

    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.

11. identified Sep 21, 2026, 09:30 PM UTC

    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.

12. identified Sep 21, 2026, 10:12 PM UTC

    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.

13. identified Sep 21, 2026, 11:06 PM UTC

    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.

14. identified Sep 21, 2026, 11:35 PM UTC

    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.

15. identified Sep 22, 2026, 12:06 AM UTC

    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.

16. monitoring Sep 22, 2026, 12:40 AM UTC

    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.

17. resolved Sep 22, 2026, 01:31 AM UTC

    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.

Read the full incident report →

Started Sep 17, 2026, 04:55 PM UTC· resolved Sep 17, 2026, 05:10 PM UTC

1. resolved Sep 17, 2026, 05:00 PM UTC

   Confluent Cloud Metrics API experienced elevated latency and error rates between 9:55 AM PDT to 10:10 AM PDT.

Read the full incident report →

Started Sep 15, 2026, 11:59 PM UTC· resolved Sep 16, 2026, 01:21 AM UTC

1. investigating Sep 15, 2026, 11:59 PM UTC

   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.

2. identified Sep 16, 2026, 12:00 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Sep 16, 2026, 12:22 AM UTC

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

4. resolved Sep 16, 2026, 01:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2026, 08:01 PM UTC· resolved Sep 09, 2026, 01:01 PM UTC

1. investigating Sep 08, 2026, 08:01 PM UTC

   We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.

2. investigating Sep 08, 2026, 08:13 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 08, 2026, 08:20 PM UTC

   A possible root cause has been identified and the Confluent Cloud team is implementing a fix

4. monitoring Sep 08, 2026, 08:30 PM UTC

   A fix has been implemented and the team is monitoring recovery.

5. resolved Sep 09, 2026, 01:01 PM UTC

   The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.

Read the full incident report →

Started Sep 08, 2026, 09:17 AM UTC· resolved Sep 09, 2026, 02:56 PM UTC

1. investigating Sep 08, 2026, 09:17 AM UTC

   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.

2. identified Sep 08, 2026, 10:37 AM UTC

   The issue has been identified and a fix is being implemented.

3. investigating Sep 08, 2026, 11:38 AM UTC

   We are currently investigating this issue.

4. identified Sep 08, 2026, 02:06 PM UTC

   The issue has been identified and a fix is being implemented.

5. identified Sep 08, 2026, 03:55 PM UTC

   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

6. identified Sep 08, 2026, 05:41 PM UTC

   We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.

7. identified Sep 09, 2026, 12:01 AM UTC

   Confluent is continuing to work on remediating the service disruption in AWS us-east-1.

8. identified Sep 09, 2026, 01:45 AM UTC

   Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.

9. monitoring Sep 09, 2026, 06:41 AM UTC

   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.

10. resolved Sep 09, 2026, 02:56 PM UTC

    The systems have recovered and Confluent Cloud is fully operational.

Read the full incident report →

Started Sep 01, 2026, 04:27 PM UTC· resolved Sep 01, 2026, 05:14 PM UTC

1. investigating Sep 01, 2026, 04:27 PM UTC

   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.

2. resolved Sep 01, 2026, 05:14 PM UTC

   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.

Read the full incident report →

Started Aug 25, 2026, 04:17 AM UTC· resolved Aug 25, 2026, 07:29 AM UTC

1. investigating Aug 25, 2026, 04:17 AM UTC

   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.

2. monitoring Aug 25, 2026, 05:28 AM UTC

   We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation.

3. resolved Aug 25, 2026, 07:29 AM UTC

   Confluent services in the Azure Southeast Asia region are now healthy and operating normally.

Read the full incident report →

Started Aug 23, 2026, 09:15 PM UTC· resolved Aug 24, 2026, 01:15 AM UTC

1. resolved Aug 23, 2026, 09:00 PM UTC

   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.

Read the full incident report →

Started Aug 20, 2026, 05:10 PM UTC· resolved Aug 20, 2026, 08:18 PM UTC

1. investigating Aug 20, 2026, 05:10 PM UTC

   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.

2. investigating Aug 20, 2026, 07:18 PM UTC

   We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.

3. resolved Aug 20, 2026, 08:18 PM UTC

   The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.

Read the full incident report →

Started Jul 17, 2026, 10:01 PM UTC· resolved Jul 18, 2026, 12:59 AM UTC

1. investigating Jul 17, 2026, 10:01 PM UTC

   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.

2. identified Jul 17, 2026, 10:54 PM UTC

   Engineers have identified and implemented a fix.

3. monitoring Jul 17, 2026, 10:55 PM UTC

   Currently, we are monitoring the results after rolling out the fix.

4. resolved Jul 18, 2026, 12:59 AM UTC

   All the statements should be running now.

Read the full incident report →

Started Jul 15, 2026, 11:33 PM UTC· resolved Jul 16, 2026, 01:14 PM UTC

1. investigating Jul 15, 2026, 11:33 PM UTC

   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.

2. resolved Jul 16, 2026, 01:14 PM UTC

   The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.

Read the full incident report →

Started Jul 13, 2026, 02:25 PM UTC· resolved Jul 13, 2026, 04:04 PM UTC

1. identified Jul 13, 2026, 02:25 PM UTC

   The issue has been identified and a fix is being implemented.

2. monitoring Jul 13, 2026, 02:36 PM UTC

   A fix has been implemented and we are monitoring the results

3. resolved Jul 13, 2026, 04:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 05:44 PM UTC· resolved Jun 29, 2026, 08:36 PM UTC

1. identified Jun 29, 2026, 05:44 PM UTC

   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.

2. resolved Jun 29, 2026, 08:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 11:40 AM UTC· resolved Jun 29, 2026, 12:50 PM UTC

1. investigating Jun 29, 2026, 11:40 AM UTC

   We are currently investigating this issue.

2. identified Jun 29, 2026, 12:04 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jun 29, 2026, 12:10 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jun 29, 2026, 12:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 25, 2026, 03:59 PM UTC· resolved Jun 25, 2026, 05:53 PM UTC

1. investigating Jun 25, 2026, 03:59 PM UTC

   We are currently investigating this issue.

2. monitoring Jun 25, 2026, 04:12 PM UTC

   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.

3. resolved Jun 25, 2026, 05:53 PM UTC

   This incident has been resolved.

Read the full incident report →