Confluent Cloud Status

Identified: A fleet-wide deployment containing a permanent fix is underway. We are continuing to monitor the rollout and will update when it is complete.

Identified: 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.

Investigating: We are currently experiencing delays in cluster provisioning in AWS. The team is currently investigating.

Resolved: This incident has been fully resolved.

Monitoring: 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.

Investigating: 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.

Investigating: 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.

Resolved: This incident has been resolved.

Monitoring: 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.

Identified: We continue to work on mitigation while some operations have been restored in AWS us-east-1.

Identified: Our team continues to actively work on mitigating the networking issue in AWS us-east-1. Progress is being made toward restoring full service.

Identified: The root cause has been identified and our team is actively working on mitigation to restore full service

Investigating: 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.