Cloud Service Outages

Incident Report for Telerik

Postmortem

Many of our systems rely on Azure Front Door (AFD) for its ability to handle high-volume, high regional availability, fast scalability, DDOS protection and much more. There was a global outage of AFD today, this has a significant cascading effect on almost every corner of the ecosystem, including some of the Telerik systems.

Here below is a quoted description from Microsoft’s Azure Status https://azure.status.microsoft/en-us/status page. You can read more after they’ve finalized their post-incident review on the https://azure.status.microsoft/en-us/status/history/ page.

‌

Azure Front Door - Connectivity issues - Observing recovery

Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue.

Affected Azure services may have included, but were not limited to:

App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID (Mobility Management Policy Service, Identity & Access Management, and User Management UX), Microsoft Purview, Microsoft Sentinel (Threat Intelligence), and Video Indexer.

Posted Oct 30, 2025 - 00:12 UTC

Resolved

Microsoft has updated their Azure Front Door status to informational, with full mitigation/recovery expected by 00:40 UTC 30 October 2025.

- Current Azure Status can be found at https://azure.status.microsoft/en-us/status
- Post INcident Review can be found at https://azure.status.microsoft/en-us/status/history/

We have seen fully reliable and stable operation for the past few hours and are updating our status to resolved.

Posted Oct 30, 2025 - 00:02 UTC

Monitoring

Microsoft has shared an update informing customers that a configuration change to Azure Front Door has been reverted. As a consequence of this change, we can confirm network traffic and API requests have returned to our backend services. You should now be able to generate new license key files, script keys, and leverage any dynamic license-related features like Page Templates.

Out of an abundance of caution, we are only updating this alert to Monitoring, rather than Resolved. We will continue to closely monitor the situation and update our status as the services are fully restored and Microsoft updates their status to Resolved.

****************************************************
From https://azure.status.microsoft/en-us/status
Updated at 21:27 UTC on 29 October, 2025
****************************************************
Current status: We initiated the deployment of our ‘last known good’ configuration, which has now successfully completed. We are currently recovering nodes and re-routing traffic through healthy nodes.

As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UTC on 29 October 2025
****************************************************

Posted Oct 29, 2025 - 21:32 UTC

Identified

Due to an ongoing global Azure outage, the ability to generate new license keys/key files, is currently unavailable. We are closely monitoring the situation and are working to restore the affected services as soon as possible.

Note: Your existing license keys and key files will continue to work as expected.

Posted Oct 29, 2025 - 20:08 UTC