Confluent experienced a major incident on October 29, 2025 affecting Confluent Cloud, lasting 7h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:55 PM UTC
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 Oct 29, 2025, 06:12 PM UTC
We are continuing to investigate this issue.
- identified Oct 29, 2025, 06:39 PM UTC
Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.
- monitoring Oct 29, 2025, 06:59 PM UTC
Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.
- monitoring Oct 29, 2025, 08:35 PM UTC
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.
- resolved Oct 30, 2025, 12:42 AM UTC
Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.