What happened
Microsoft Azure: Front Door: network control-plane failure plus latent routing configuration. Scope: Multi-region.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Microsoft Azure: Front Door: network control-plane failure plus latent routing configuration. Scope: Multi-region.
Severe storm
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Microsoft Azure: Front Door: network control-plane failure plus latent routing configuration. Scope: Multi-region.
Azure Front Door, Azure CDN, Azure Portal.
24 catalogued services run on Microsoft Azure (inferred). Hit: Multi-region.
Resolved after 7h 58m.
Center: Microsoft Azure. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.
Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.
Failure modes as stated in the vendor's own post-incident report (Meltdown Index).
Correlation is not causation
Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.
At around 11:45 UTC, as the Network DDoS protection service was disengaging and resuming default traffic routing to the Azure Front Door service, the network routes could not be updated within one specific site in Europe. This happened because of Network control plane failures to that specific site, due to a local power outage. Consequently, traffic inside Europe continued to be forwarded to AFD through our DDoS protection services, instead of returning directly to AFD. These control plane failures were not caused or related to the initial DDoS trigger event – and in isolation, would not have caused any impact. However, an unrelated latent network configuration issue caused traffic from outside Europe to be routed to the DDoS protection system within Europe.
Impact started 11:45 UTC; vast majority mitigated by 13:58 UTC; isolated connection failures for a subset of customers without retry logic until 19:43 UTC. A volumetric DDoS between 10:15 and 10:45 UTC was automatically mitigated and is described by Microsoft as a trigger, not the control-plane failure itself.
Verbatim excerpt from Azure Post Incident Review — KTY1-HW8 (30 Jul 2024).
100% similar · same provider
Front Door: manual metadata cleanup bypassed protection
Config pushControl plane
90% similar · same provider
ARM control plane blocked by a global Cosmos DB misconfiguration
Config pushControl plane
75% similar · same provider
Front Door: incompatible metadata across two control-plane versions
Control planeConfig pushCascade
Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.
Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Microsoft Azure.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Microsoft Azure in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/azure-afd-2024-07-30/"><img src="https://www.chyp.ai/dissect/m/azure-afd-2024-07-30/card.svg" alt="Front Door: network control-plane failure plus latent routi… · ORBIT Outage Dissector" width="600"></a>