Confluent Cloud Status

Resolved: Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.

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

Monitoring: Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.

Identified: Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.

Investigating: We are continuing to investigate this issue.

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

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating the issue. In the meantime, customers can use the CLI to manage the resources.

Investigating: We are currently investigating the root cause.

Resolved: This incident has been resolved.

Identified: Dedicated private networks and dedicated Kafka clusters provisioning with PrivateLink or VNet Peering are unavailable in the Azure eastus region.

Identified: Provisioning delays have been partially mitigated, but there may still be delays for eastus region.

Identified: We've identified a mitigation method and are rolling this out across affected networks.

Identified: We are experiencing provisioning delays in Azure eastus region.