What happened
Microsoft Azure: Front Door: manual metadata cleanup bypassed protection. Scope: Multi-region (Africa, Europe, APAC, Middle East).
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Microsoft Azure: Front Door: manual metadata cleanup bypassed protection. Scope: Multi-region (Africa, Europe, APAC, Middle East).
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: manual metadata cleanup bypassed protection. Scope: Multi-region (Africa, Europe, APAC, Middle East).
Azure Front Door, Azure CDN, Azure Portal, Microsoft management portals.
24 catalogued services run on Microsoft Azure (inferred). Hit: Multi-region (Africa, Europe, APAC, Middle East).
Resolved after 8h 10m.
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.
A manual cleanup of stuck tenant metadata bypassed our configuration protection layer, allowing incompatible metadata to propagate beyond our canary edge sites.
Official window 07:50–16:00 UTC; availability restored by 12:50 UTC, latency baseline by 16:00 UTC. The ‘manual cleanup’ wording is from Microsoft’s 4 Nov 2025 Tech Community post (HTTP 200): https://techcommunity.microsoft.com/blog/azurenetworkingblog/azure-front-door-implementing-lessons-learned-following-october-outages/4479416 — also https://aka.ms/AIR/QNBQ-5W8.
Verbatim excerpt from Azure Post Incident Review — QNBQ-5W8 (9 Oct 2025).
100% similar · same provider
Front Door: network control-plane failure plus latent routing configuration
Control planeConfig push
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-2025-10-09/"><img src="https://www.chyp.ai/dissect/m/azure-afd-2025-10-09/card.svg" alt="Front Door: manual metadata cleanup bypassed protection · ORBIT Outage Dissector" width="600"></a>