Degraded Flink statements in Azure

Final update

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

1. Resolved · Oct 30, 00:42 UTC
   Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.
2. Monitoring · Oct 29, 20:35 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.
3. Monitoring · Oct 29, 18:59 UTC
   Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.
4. Identified · Oct 29, 18:39 UTC
   Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.
5. Investigating · Oct 29, 18:12 UTC
   We are continuing to investigate this issue.
6. Investigating · Oct 29, 16:55 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