CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report

Front Door: incompatible metadata across two control-plane versions

Microsoft Azure resolved M8.4 Severe storm 2025-10-29

Microsoft Azure: Front Door: incompatible metadata across two control-plane versions. Scope: Global.

M8.4

Severe storm

How CHYP Magnitude works

  • 8h 24mDurationstart → resolved
  • 6Systems namedfrom the source
  • 7Places named7 on the map
  • 24Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Oct 29, 8 AMOct 29, 10 AMOct 29, 12 PMOct 29, 1 PMOct 29, 3 PMOct 29, 4 PM Official statusOct 29, 8:41 AM PT · Impact begins (vendor-stated)Oct 29, 5:05 PM PT · Mitigated (vendor-stated)Network & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startresolved ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Microsoft Azure: Front Door: incompatible metadata across two control-plane versions. Scope: Global.

What broke

Azure Front Door, Azure CDN, Azure Portal, Microsoft Entra and 2 more.

Who was hit

24 catalogued services run on Microsoft Azure (inferred). Hit: Global.

How it recovered

Resolved after 8h 24m.

2Blast radius

Elastic Cloud · Degraded / minor incidentElastic CloudJFrog · MaintenanceJFrogAiven · OperationalAivenGitHub · OperationalGitHubGitHub Copilot · OperationalGitHub CopilotGrafana Cloud · OperationalGrafana CloudLinkedIn · OperationalLinkedInMongoDB Atlas · OperationalMongoDB AtlasOpenAI (ChatGPT & API) · OperationalOpenAI (ChatGPT…Snowflake · OperationalSnowflakeAdobe Creative Cloud · no official feed / staleAdobe Creative …Bitwarden · no official feed / staleBitwardenCostco · no official feed / staleCostcoDatabricks · no official feed / staleDatabricksDatadog · no official feed / staleDatadogDocusign · no official feed / staleDocusignMicrosoft 365 · no official feed / staleMicrosoft 365Microsoft Teams · no official feed / staleMicrosoft TeamsMinecraft · no official feed / staleMinecraftNeon · no official feed / staleNeonOutlook.com · no official feed / staleOutlook.comRedis Cloud · no official feed / staleRedis CloudWalmart · no official feed / staleWalmartXbox Network · no official feed / staleXbox NetworkMicrosoft Azu…24 dependents

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.

3Blast map

North America · vendor-stated scope: globalSouth America · vendor-stated scope: globalEurope · vendor-stated scope: globalAfrica · vendor-stated scope: globalMiddle East · vendor-stated scope: globalAsia · vendor-stated scope: globalOceania · vendor-stated scope: global
  1. North America
  2. South America
  3. Europe
  4. Africa
  5. Middle East
  6. Asia
  7. Oceania

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane couplingvendor post-incident report (Meltdown Index)
  • Config propagationvendor post-incident report (Meltdown Index)
  • Dependency cascadevendor post-incident report (Meltdown Index)
  • Retry amplificationno sign
  • Capacity exhaustionno sign

Failure modes as stated in the vendor's own post-incident report (Meltdown Index).

5Evidence matrix

Official statusOfficial status · Oct 29, 2:41 AM PT: 0 itemsOfficial status · Oct 29, 3:17 AM PT: 0 itemsOfficial status · Oct 29, 3:53 AM PT: 0 itemsOfficial status · Oct 29, 4:29 AM PT: 0 itemsOfficial status · Oct 29, 5:05 AM PT: 0 itemsOfficial status · Oct 29, 5:41 AM PT: 0 itemsOfficial status · Oct 29, 6:17 AM PT: 0 itemsOfficial status · Oct 29, 6:53 AM PT: 0 itemsOfficial status · Oct 29, 7:29 AM PT: 0 itemsOfficial status · Oct 29, 8:05 AM PT: 0 itemsOfficial status · Oct 29, 8:41 AM PT: 1 itemOfficial status · Oct 29, 9:17 AM PT: 0 itemsOfficial status · Oct 29, 9:53 AM PT: 0 itemsOfficial status · Oct 29, 10:29 AM PT: 0 itemsOfficial status · Oct 29, 11:05 AM PT: 0 itemsOfficial status · Oct 29, 11:41 AM PT: 0 itemsOfficial status · Oct 29, 12:17 PM PT: 0 itemsOfficial status · Oct 29, 12:53 PM PT: 0 itemsOfficial status · Oct 29, 1:29 PM PT: 0 itemsOfficial status · Oct 29, 2:05 PM PT: 0 itemsOfficial status · Oct 29, 2:41 PM PT: 0 itemsOfficial status · Oct 29, 3:17 PM PT: 0 itemsOfficial status · Oct 29, 3:53 PM PT: 0 itemsOfficial status · Oct 29, 4:29 PM PT: 0 itemsNetwork & routingNetwork & routing · Oct 29, 2:41 AM PT: 0 itemsNetwork & routing · Oct 29, 3:17 AM PT: 0 itemsNetwork & routing · Oct 29, 3:53 AM PT: 0 itemsNetwork & routing · Oct 29, 4:29 AM PT: 0 itemsNetwork & routing · Oct 29, 5:05 AM PT: 0 itemsNetwork & routing · Oct 29, 5:41 AM PT: 0 itemsNetwork & routing · Oct 29, 6:17 AM PT: 0 itemsNetwork & routing · Oct 29, 6:53 AM PT: 0 itemsNetwork & routing · Oct 29, 7:29 AM PT: 0 itemsNetwork & routing · Oct 29, 8:05 AM PT: 0 itemsNetwork & routing · Oct 29, 8:41 AM PT: 0 itemsNetwork & routing · Oct 29, 9:17 AM PT: 0 itemsNetwork & routing · Oct 29, 9:53 AM PT: 0 itemsNetwork & routing · Oct 29, 10:29 AM PT: 0 itemsNetwork & routing · Oct 29, 11:05 AM PT: 0 itemsNetwork & routing · Oct 29, 11:41 AM PT: 0 itemsNetwork & routing · Oct 29, 12:17 PM PT: 0 itemsNetwork & routing · Oct 29, 12:53 PM PT: 0 itemsNetwork & routing · Oct 29, 1:29 PM PT: 0 itemsNetwork & routing · Oct 29, 2:05 PM PT: 0 itemsNetwork & routing · Oct 29, 2:41 PM PT: 0 itemsNetwork & routing · Oct 29, 3:17 PM PT: 0 itemsNetwork & routing · Oct 29, 3:53 PM PT: 0 itemsNetwork & routing · Oct 29, 4:29 PM PT: 0 itemsEarly signalsEarly signals · Oct 29, 2:41 AM PT: 0 itemsEarly signals · Oct 29, 3:17 AM PT: 0 itemsEarly signals · Oct 29, 3:53 AM PT: 0 itemsEarly signals · Oct 29, 4:29 AM PT: 0 itemsEarly signals · Oct 29, 5:05 AM PT: 0 itemsEarly signals · Oct 29, 5:41 AM PT: 0 itemsEarly signals · Oct 29, 6:17 AM PT: 0 itemsEarly signals · Oct 29, 6:53 AM PT: 0 itemsEarly signals · Oct 29, 7:29 AM PT: 0 itemsEarly signals · Oct 29, 8:05 AM PT: 0 itemsEarly signals · Oct 29, 8:41 AM PT: 0 itemsEarly signals · Oct 29, 9:17 AM PT: 0 itemsEarly signals · Oct 29, 9:53 AM PT: 0 itemsEarly signals · Oct 29, 10:29 AM PT: 0 itemsEarly signals · Oct 29, 11:05 AM PT: 0 itemsEarly signals · Oct 29, 11:41 AM PT: 0 itemsEarly signals · Oct 29, 12:17 PM PT: 0 itemsEarly signals · Oct 29, 12:53 PM PT: 0 itemsEarly signals · Oct 29, 1:29 PM PT: 0 itemsEarly signals · Oct 29, 2:05 PM PT: 0 itemsEarly signals · Oct 29, 2:41 PM PT: 0 itemsEarly signals · Oct 29, 3:17 PM PT: 0 itemsEarly signals · Oct 29, 3:53 PM PT: 0 itemsEarly signals · Oct 29, 4:29 PM PT: 0 itemsNews & chatterNews & chatter · Oct 29, 2:41 AM PT: 0 itemsNews & chatter · Oct 29, 3:17 AM PT: 0 itemsNews & chatter · Oct 29, 3:53 AM PT: 0 itemsNews & chatter · Oct 29, 4:29 AM PT: 0 itemsNews & chatter · Oct 29, 5:05 AM PT: 0 itemsNews & chatter · Oct 29, 5:41 AM PT: 0 itemsNews & chatter · Oct 29, 6:17 AM PT: 0 itemsNews & chatter · Oct 29, 6:53 AM PT: 0 itemsNews & chatter · Oct 29, 7:29 AM PT: 0 itemsNews & chatter · Oct 29, 8:05 AM PT: 0 itemsNews & chatter · Oct 29, 8:41 AM PT: 0 itemsNews & chatter · Oct 29, 9:17 AM PT: 0 itemsNews & chatter · Oct 29, 9:53 AM PT: 0 itemsNews & chatter · Oct 29, 10:29 AM PT: 0 itemsNews & chatter · Oct 29, 11:05 AM PT: 0 itemsNews & chatter · Oct 29, 11:41 AM PT: 0 itemsNews & chatter · Oct 29, 12:17 PM PT: 0 itemsNews & chatter · Oct 29, 12:53 PM PT: 0 itemsNews & chatter · Oct 29, 1:29 PM PT: 0 itemsNews & chatter · Oct 29, 2:05 PM PT: 0 itemsNews & chatter · Oct 29, 2:41 PM PT: 0 itemsNews & chatter · Oct 29, 3:17 PM PT: 0 itemsNews & chatter · Oct 29, 3:53 PM PT: 0 itemsNews & chatter · Oct 29, 4:29 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Oct 29, 2:41 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 3:17 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 3:53 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 4:29 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 5:05 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 5:41 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 6:17 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 6:53 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 7:29 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 8:05 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 8:41 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 9:17 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 9:53 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 10:29 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 11:05 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 11:41 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 12:17 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 12:53 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 1:29 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 2:05 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 2:41 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 3:17 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 3:53 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 4:29 PM PT: 0 itemsOct 29, 2:41 AM PTOct 29, 5:05 PM PT

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.

6In the vendor's words

A specific sequence of customer configuration changes, performed across two different control plane build versions, resulted in incompatible customer configuration metadata being generated. These customer configuration changes themselves were valid and non-malicious – however they produced metadata that, when deployed to edge site servers, exposed a latent bug in the data plane.

Official window 15:41 UTC 29 Oct–00:05 UTC 30 Oct. Microsoft also published a lessons-learned post: https://techcommunity.microsoft.com/blog/azurenetworkingblog/azure-front-door-implementing-lessons-learned-following-october-outages/4479416

Verbatim excerpt from Azure Post Incident Review — YKYN-BWZ (29–30 Oct 2025).

7Historical twins

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.

Cloudy_Day take

  • Control plane on the critical path again. When the management layer sneezes, the data plane shouldn't catch a cold.
  • Longer than 15 of 19 indexed control-plane meltdowns with a stated duration.

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.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Microsoft Azure in the War Room →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/m/azure-afd-2025-10-29/"><img src="https://www.chyp.ai/dissect/m/azure-afd-2025-10-29/card.svg" alt="Front Door: incompatible metadata across two control-plane … · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Taken from the vendor's own post-incident report; quotes are verbatim excerpts.
  • Dependents are today's inferred catalogue, not who was affected on the day.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.