All Systems Operational

About This Site

Welcome to Confluent Cloud's status page. Here you will find high level availability information for the Confluent Cloud managed service. Visit https://confluent.cloud to manage your Confluent Cloud clusters.

Confluent Cloud Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Sep 22, 2026

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

This is associated with an ongoing Microsoft Azure service disruption in that region. We are actively engaged with Microsoft Azure.
Sep 22, 15:09 UTC
Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Resolved - This incident has been resolved. All affected services, including Flink in AWS us-west-2, have fully recovered, and no further customer impact is expected. No action is required from customers.
Sep 22, 01:31 UTC
Monitoring - All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.
Sep 22, 00:40 UTC
Update - Confluent is continuing to monitor recovered services and complete recovery for a small number of Flink customers in AWS us-west-2 that may still be experiencing degraded jobs. We are actively working to fully restore them and will post the next update by 00:30 UTC, or sooner if service is fully restored.
Sep 22, 00:06 UTC
Update - All affected services have recovered with the exception of a small number of Flink customers in AWS us-west-2 that may still experience degraded jobs while we complete recovery. We are actively working to fully restore them and will post the next update by 00:00 UTC, or sooner if service is fully restored.
Sep 21, 23:35 UTC
Update - Flink in AWS us-west-2 is still recovering as we continue to restore full service: while some jobs may start to recover, others may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 23:30 UTC or sooner if recovery completes sooner.
Sep 21, 23:06 UTC
Update - Flink in AWS us-west-2 is still recovering as we continue to restore full service: running jobs may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 22:30 UTC or sooner if recovery completes sooner.
Sep 21, 22:12 UTC
Update - Most affected services are recovering and we are continuing to monitor for stability. Flink in AWS us-west-2 is still recovering and running jobs may remain degraded with new submissions still failing. We will post the next update by 22:00 UTC or sooner if the situation changes.
Sep 21, 21:30 UTC
Identified - We have applied a mitigation and most affected services are beginning to recover. Flink in AWS us-west-2 will continue to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. We will post the next update by 21:30 UTC, or sooner if service is restored.
Sep 21, 20:56 UTC
Update - We are continuing to work to resolve the incident and do not yet have a confirmed mitigation. Impact remains as previously described. We will post the next update by 20:30 UTC, or sooner if the situation changes.
Sep 21, 20:03 UTC
Update - We are continuing to validate several proposed mitigations to address the ongoing incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. We do not yet have a confirmed fix in place. We will post the next update by 20:00 UTC, or sooner if service is restored.
Sep 21, 19:33 UTC
Update - We are continuing to investigate an incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. Several potential mitigations remain under active testing and validation. We do not yet have a confirmed fix in place. We will post the next update by 19:30 UTC, or sooner if service is restored.
Sep 21, 19:08 UTC
Update - We are testing and validating several potential mitigations in parallel to restore the Confluent Cloud Console and affected services. We do not yet have a confirmed fix in place and are continuing to investigate. We will post the next update by 19:00 UTC, or sooner if service is restored.
Sep 21, 18:31 UTC
Update - We have refined the scope of customer impact and continue to work on a mitigation.

Impacted Services:
- Confluent Cloud Console (web UI), all regions: broad degradation. Customers may be unable to view or manage their resources in the Console.
- Schema Registry, AWS us-west-2: a subset of Schema Registry clusters are unavailable.
- Flink, AWS us-west-2: all running jobs are degraded, and new job submissions will fail.
- Cluster Linking, AWS us-west-2: links to Enterprise clusters are impacted.
- Topic operations, AWS us-west-2: unavailable for Freight and some Basic and Standard clusters.
- Tableflow, AWS us-west-2: All operations are unavailable (additionally, topics utilizing the us-west-2 Schema Registry may be impacted)
- Connect, AWS us-west-2: Some connectors dependent on unavailable Schema Registry clusters may be affected
- Notifications, all regions: delivery is delayed. Customers may not receive notifications and alerts until the backlog clears.

Confirmed not impacted:
- Regular produce and consume operations on Kafka clusters are not affected.
- Topic-related operations on Enterprise and Dedicated clusters are not affected.

We are actively applying a mitigation. We will post the next update by 18:30 UTC, or sooner if service is restored.
Sep 21, 18:01 UTC
Update - We are confirming a contributing factor and applying a mitigation intended to restore Confluent Cloud services. We will post an update by 17:45 UTC, or sooner if service is restored.
Sep 21, 17:04 UTC
Update - We have made progress in identifying the cause of the disruption in AWS us-west-2 and are working to confirm the safest path to mitigation. Some customers in this region may continue to experience errors or degraded performance. We will post the next update by 17:00 UTC, or sooner if mitigation is achieved.
Sep 21, 16:32 UTC
Update - Multiple Confluent Cloud services in the AWS us-west-2 region are experiencing elevated error rates and service disruption. Impacted customers may see failed or slow requests to Kafka clusters, Connect, and Flink in this region. The Confluent Cloud UI is also degraded and visibility to clusters outside of us-west-2 may be impacted as well. We are actively investigating and will post the next update by 16:30 UTC, or sooner if we have new information.
Sep 21, 16:15 UTC
Investigating - Starting today at 15:26 UTC, Confluent Cloud is experiencing an incident involving multiple service disruptions in the AWS us-west-2 region. We are investigating the issue and will provide further updates shortly.
Sep 21, 16:04 UTC

Sep 21, 2026

Sep 20, 2026

No incidents reported.

Sep 19, 2026

No incidents reported.

Sep 18, 2026

No incidents reported.

Sep 17, 2026

Confluent Cloud Metrics API experienced elevated latency and error rates
Resolved - Confluent Cloud Metrics API experienced elevated latency and error rates between 9:55 AM PDT to 10:10 AM PDT.
Sep 17, 17:00 UTC

Sep 16, 2026

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

Sep 15, 2026

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

No incidents reported.

Sep 9, 2026

Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Resolved - The systems have recovered and Confluent Cloud is fully operational.
Sep 9, 14:56 UTC
Monitoring - We have applied a mitigation for the issue affecting Schema Registry, Authentication, ksqlDB, Flink, and Kafka operations in AWS us-east-1. Services are recovering and we are monitoring closely.
Sep 9, 06:41 UTC
Update - Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.
Sep 9, 01:45 UTC
Update - Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
Sep 9, 00:01 UTC
Update - We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.
Sep 8, 17:41 UTC
Update - We continue to work on remediating the service disruption in AWS us-east-1.

Confirmed impact:

- Authentication — a subset of requests may fail
- Schema Registry — authorization errors on a subset of requests
- ksqlDB — a subset of queries/requests may be affected
- Flink — statement management operations (create/update/delete) are degraded, and some running Flink jobs may fail or restart
- Kafka operations (create, delete etc)

Not impacted: Kafka cluster data-plane operations are not affected by this incident. This issue is isolated to the AWS us-east-1 region; other regions are unaffected
Sep 8, 15:55 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 8, 14:06 UTC
Investigating - We are currently investigating this issue.
Sep 8, 11:38 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 8, 10:37 UTC
Investigating - We are investigating a service disruption affecting multiple services in AWS us-east-1 region. Affected customers may experience authentication failures, errors accessing Schema Registry, or issues with KSQL and Flink workloads. We are actively investigating the root cause and working toward mitigation.
Sep 8, 09:17 UTC
Connectivity degradation - AWS us-east-1
Resolved - The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.
Sep 9, 13:01 UTC
Monitoring - A fix has been implemented and the team is monitoring recovery.
Sep 8, 20:30 UTC
Identified - A possible root cause has been identified and the Confluent Cloud team is implementing a fix
Sep 8, 20:20 UTC
Update - We are continuing to investigate this issue.
Sep 8, 20:13 UTC
Investigating - We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.
Sep 8, 20:01 UTC

Sep 8, 2026

Incident History Powered by Atlassian Statuspage