CHYP.ai · ORBIT // Cloudy_Day Security Suite

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

Front Door: network control-plane failure plus latent routing configuration

Microsoft Azure resolved M7.0 Severe storm 2024-07-30

Microsoft Azure: Front Door: network control-plane failure plus latent routing configuration. Scope: Multi-region.

M7.0

Severe storm

How CHYP Magnitude works

  • 7h 58mDurationstart → resolved
  • 3Systems namedfrom the source
  • 1Places named1 on the map
  • 24Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Jul 30, 4 AMJul 30, 6 AMJul 30, 7 AMJul 30, 9 AMJul 30, 10 AMJul 30, 12 PM Official statusJul 30, 4:45 AM PT · Impact begins (vendor-stated)Jul 30, 12:43 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: network control-plane failure plus latent routing configuration. Scope: Multi-region.

What broke

Azure Front Door, Azure CDN, Azure Portal.

Who was hit

24 catalogued services run on Microsoft Azure (inferred). Hit: Multi-region.

How it recovered

Resolved after 7h 58m.

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

Europe · congestion centered on a European site,…
  1. Europe

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)
  • Retry amplificationno sign
  • Dependency cascadeno sign
  • Capacity exhaustionno sign

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

5Evidence matrix

Official statusOfficial status · Jul 29, 10:45 PM PT: 0 itemsOfficial status · Jul 29, 11:19 PM PT: 0 itemsOfficial status · Jul 29, 11:54 PM PT: 0 itemsOfficial status · Jul 30, 12:29 AM PT: 0 itemsOfficial status · Jul 30, 1:04 AM PT: 0 itemsOfficial status · Jul 30, 1:39 AM PT: 0 itemsOfficial status · Jul 30, 2:14 AM PT: 0 itemsOfficial status · Jul 30, 2:49 AM PT: 0 itemsOfficial status · Jul 30, 3:24 AM PT: 0 itemsOfficial status · Jul 30, 3:59 AM PT: 0 itemsOfficial status · Jul 30, 4:34 AM PT: 1 itemOfficial status · Jul 30, 5:09 AM PT: 0 itemsOfficial status · Jul 30, 5:44 AM PT: 0 itemsOfficial status · Jul 30, 6:18 AM PT: 0 itemsOfficial status · Jul 30, 6:53 AM PT: 0 itemsOfficial status · Jul 30, 7:28 AM PT: 0 itemsOfficial status · Jul 30, 8:03 AM PT: 0 itemsOfficial status · Jul 30, 8:38 AM PT: 0 itemsOfficial status · Jul 30, 9:13 AM PT: 0 itemsOfficial status · Jul 30, 9:48 AM PT: 0 itemsOfficial status · Jul 30, 10:23 AM PT: 0 itemsOfficial status · Jul 30, 10:58 AM PT: 0 itemsOfficial status · Jul 30, 11:33 AM PT: 0 itemsOfficial status · Jul 30, 12:08 PM PT: 0 itemsNetwork & routingNetwork & routing · Jul 29, 10:45 PM PT: 0 itemsNetwork & routing · Jul 29, 11:19 PM PT: 0 itemsNetwork & routing · Jul 29, 11:54 PM PT: 0 itemsNetwork & routing · Jul 30, 12:29 AM PT: 0 itemsNetwork & routing · Jul 30, 1:04 AM PT: 0 itemsNetwork & routing · Jul 30, 1:39 AM PT: 0 itemsNetwork & routing · Jul 30, 2:14 AM PT: 0 itemsNetwork & routing · Jul 30, 2:49 AM PT: 0 itemsNetwork & routing · Jul 30, 3:24 AM PT: 0 itemsNetwork & routing · Jul 30, 3:59 AM PT: 0 itemsNetwork & routing · Jul 30, 4:34 AM PT: 0 itemsNetwork & routing · Jul 30, 5:09 AM PT: 0 itemsNetwork & routing · Jul 30, 5:44 AM PT: 0 itemsNetwork & routing · Jul 30, 6:18 AM PT: 0 itemsNetwork & routing · Jul 30, 6:53 AM PT: 0 itemsNetwork & routing · Jul 30, 7:28 AM PT: 0 itemsNetwork & routing · Jul 30, 8:03 AM PT: 0 itemsNetwork & routing · Jul 30, 8:38 AM PT: 0 itemsNetwork & routing · Jul 30, 9:13 AM PT: 0 itemsNetwork & routing · Jul 30, 9:48 AM PT: 0 itemsNetwork & routing · Jul 30, 10:23 AM PT: 0 itemsNetwork & routing · Jul 30, 10:58 AM PT: 0 itemsNetwork & routing · Jul 30, 11:33 AM PT: 0 itemsNetwork & routing · Jul 30, 12:08 PM PT: 0 itemsEarly signalsEarly signals · Jul 29, 10:45 PM PT: 0 itemsEarly signals · Jul 29, 11:19 PM PT: 0 itemsEarly signals · Jul 29, 11:54 PM PT: 0 itemsEarly signals · Jul 30, 12:29 AM PT: 0 itemsEarly signals · Jul 30, 1:04 AM PT: 0 itemsEarly signals · Jul 30, 1:39 AM PT: 0 itemsEarly signals · Jul 30, 2:14 AM PT: 0 itemsEarly signals · Jul 30, 2:49 AM PT: 0 itemsEarly signals · Jul 30, 3:24 AM PT: 0 itemsEarly signals · Jul 30, 3:59 AM PT: 0 itemsEarly signals · Jul 30, 4:34 AM PT: 0 itemsEarly signals · Jul 30, 5:09 AM PT: 0 itemsEarly signals · Jul 30, 5:44 AM PT: 0 itemsEarly signals · Jul 30, 6:18 AM PT: 0 itemsEarly signals · Jul 30, 6:53 AM PT: 0 itemsEarly signals · Jul 30, 7:28 AM PT: 0 itemsEarly signals · Jul 30, 8:03 AM PT: 0 itemsEarly signals · Jul 30, 8:38 AM PT: 0 itemsEarly signals · Jul 30, 9:13 AM PT: 0 itemsEarly signals · Jul 30, 9:48 AM PT: 0 itemsEarly signals · Jul 30, 10:23 AM PT: 0 itemsEarly signals · Jul 30, 10:58 AM PT: 0 itemsEarly signals · Jul 30, 11:33 AM PT: 0 itemsEarly signals · Jul 30, 12:08 PM PT: 0 itemsNews & chatterNews & chatter · Jul 29, 10:45 PM PT: 0 itemsNews & chatter · Jul 29, 11:19 PM PT: 0 itemsNews & chatter · Jul 29, 11:54 PM PT: 0 itemsNews & chatter · Jul 30, 12:29 AM PT: 0 itemsNews & chatter · Jul 30, 1:04 AM PT: 0 itemsNews & chatter · Jul 30, 1:39 AM PT: 0 itemsNews & chatter · Jul 30, 2:14 AM PT: 0 itemsNews & chatter · Jul 30, 2:49 AM PT: 0 itemsNews & chatter · Jul 30, 3:24 AM PT: 0 itemsNews & chatter · Jul 30, 3:59 AM PT: 0 itemsNews & chatter · Jul 30, 4:34 AM PT: 0 itemsNews & chatter · Jul 30, 5:09 AM PT: 0 itemsNews & chatter · Jul 30, 5:44 AM PT: 0 itemsNews & chatter · Jul 30, 6:18 AM PT: 0 itemsNews & chatter · Jul 30, 6:53 AM PT: 0 itemsNews & chatter · Jul 30, 7:28 AM PT: 0 itemsNews & chatter · Jul 30, 8:03 AM PT: 0 itemsNews & chatter · Jul 30, 8:38 AM PT: 0 itemsNews & chatter · Jul 30, 9:13 AM PT: 0 itemsNews & chatter · Jul 30, 9:48 AM PT: 0 itemsNews & chatter · Jul 30, 10:23 AM PT: 0 itemsNews & chatter · Jul 30, 10:58 AM PT: 0 itemsNews & chatter · Jul 30, 11:33 AM PT: 0 itemsNews & chatter · Jul 30, 12:08 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Jul 29, 10:45 PM PT: 0 itemsCoincidence (KEV) · Jul 29, 11:19 PM PT: 0 itemsCoincidence (KEV) · Jul 29, 11:54 PM PT: 0 itemsCoincidence (KEV) · Jul 30, 12:29 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 1:04 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 1:39 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 2:14 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 2:49 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 3:24 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 3:59 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 4:34 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 5:09 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 5:44 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 6:18 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 6:53 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 7:28 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 8:03 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 8:38 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 9:13 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 9:48 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 10:23 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 10:58 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 11:33 AM PT: 0 itemsCoincidence (KEV) · Jul 30, 12:08 PM PT: 0 itemsJul 29, 10:45 PM PTJul 30, 12:43 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

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).

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 13 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-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>

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.