Confluent Cloud reported this major-impact incident on its official status page on Oct 9, 2026, 23:03 UTC. It has not been marked resolved yet.
Right now Confluent Cloud is having a partial outage. Live Confluent Cloud status →
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.
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.
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.
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.
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.
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.
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.
Azure has identified the issue and recovery actions are underway
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.
Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Confluent Cloud reported 16 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 4h 1m. See Confluent Cloud's uptime and incident history