Azure Front Door outage: a DDoS attack exposes a network misconfiguration
A DDoS attack against Microsoft's network triggered congestion that a network misconfiguration turned into an outage of Azure Front Door, Azure CDN and parts of Microsoft 365 for about two hours, with lingering timeouts for some customers.
- Security:
- Confirmed malicious activity
- Started
- Jul 30, 2024, 11:45 UTC
- Last low-rate timeouts ended
- Jul 30, 2024, 19:43 UTC
- Duration
- 2 h 13 minto: Most impact mitigated7 h 58 min to: Last low-rate timeouts ended
- Full recovery
- Complete
- Geographic scope
- Global
- Last verified
- 2 sources
What happened
- Systems and services affected
- Azure Front DoorAzure CDNAzure PortalMicrosoft 365 (subset)Microsoft Purview (subset)
- Kind of failure
- Configuration change
- Sector
- Cloud infrastructure
- Provider report
- Published
- Provider incident IDs
- KTY1-HW8
- Status and recovery
- Resolved. Rerouting traffic mitigated most impact by 13:58 UTC. Engineers then found a device in Europe that was not obeying control-plane commands and removed it from the network by 19:32 UTC; remaining timeouts ended at 19:43 UTC.[1]
Most impact ended by 13:58 UTC; a smaller set of customers saw low-rate timeouts until 19:43 UTC.
What caused it?
Root cause: ConfirmedMicrosoft says a DDoS attack "was merely a trigger event." The underlying cause was that "a network misconfiguration caused congestion and packet loss for AFD frontends," starting in Europe and spreading across regions.[1]
Provider report: Published. Microsoft published a post-incident review under tracking ID KTY1-HW8.[1]
Was it malicious?
Confirmed malicious activityMicrosoft confirms a DDoS attack, which it mitigated, and calls it the trigger. It attributes the outage itself to a network misconfiguration.[1]
How the failure happened
- 1TriggerDDoS attack
- 2FailureNetwork misconfiguration
- 3SpreadSpread across regions
- Affected5 services and systems
Evidence for each step
- 1
- 2Network misconfiguration. Caused congestion and packet loss for Front Door frontends[1]Led from step 1: Stated in a provider report or official record.
- 3Spread across regions. Starting in Europe[1]Led from step 2: Stated in a provider report or official record.
Only steps the sources state are drawn. Affected services are listed under What happened.
Explanation
Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.
Plain language: what happened and why people were affected.
On July 30, 2024, some Microsoft cloud services, including parts of Microsoft 365 and the Azure portal, had connection problems for about two hours.
Attackers flooded Microsoft's network with traffic. Microsoft's defenses handled the attack itself, but a mistake in how part of the network was set up caused congestion in Europe that spread to other regions.
So the attack was real, but Microsoft says the outage happened because of its own network setup.
Confirmed and unknown
Confirmed
- ConfirmedA DDoS attack occurred and was mitigated; Microsoft calls it "merely a trigger event."[1]Said by: Microsoft · Evidence: Official
- ConfirmedA network misconfiguration caused congestion and packet loss for Azure Front Door frontends.[1]Said by: Microsoft · Evidence: Official
- ConfirmedA device in Europe was not obeying control-plane commands and was removed from the network.[1]Said by: Microsoft · Evidence: Official
- ConfirmedMost impact ended by 13:58 UTC; some customers saw low-rate timeouts until 19:43 UTC.[1]Said by: Microsoft · Evidence: Official
Still unknown
No open questions: the provider has published a full account.
Timeline
Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.
- First observedJul 30, 2024, 11:45 UTC
- AcknowledgedNot documented
- MitigationJul 30, 2024, 13:58 UTC
- RecoveryJul 30, 2024, 19:32 UTC
- ResolvedJul 30, 2024, 19:43 UTC
- Incident reportPublished, date not shown
- First observedImpact begins: connection timeouts for Azure Front Door and CDN.[1]
- MitigationMost impact mitigated by rerouting traffic.[1]
- RecoveryMisbehaving device in Europe removed from the network.[1]
- ResolvedRemaining low-rate timeouts end.[1]
- Start to: Most impact mitigated2 h 13 min
- Start to: Last low-rate timeouts ended7 h 58 min
Related incidents
Links stated by providers or officials carry their evidence label. “Similar failure” is a comparison of documented causes, not a causal link.
Evidence and sources
Grouped by type of evidence. Numbers match the citations above.
Primary: provider and official sources
Published by the provider or agency itself: incident reports, status records, advisories, statements.
- 1.Post Incident Review (PIR): Azure Front Door, Connectivity issues in multiple regions (KTY1-HW8) (opens in a new tab)Microsoft Azure · Provider report · Published · Accessed
- 2.Post Incident Review (PIR): Azure Front Door, Connectivity issues across multiple regions (YKYN-BWZ) (opens in a new tab)Microsoft Azure · Provider report · Published · Accessed
Last verified against these sources on Nov 14, 2026.