Microsoft mitigated a 2.4 Tbps DDoS attack earlier this year

Microsoft mitigated the largest Distributed Denial-of-Service (DDoS) attack on record earlier this year. The attack targeted an unnamed Azure customer in Europe and peaked at a bandwidth of 2.4 terabytes per second (Tbps). That attack bandwidth is 140% higher than the previous high mark that Microsoft recorded. Microsoft breaks down the attack and how it protected the targeted company in an Azure blog post. The attack was mitigated by Microsoft in the last week of August 2021.

According to Microsoft, the attack lasted longer than 10 minutes and included short bursts of high traffic. The bursts hit peaks of 2.4 Tbps, 0.55 Tbps, and 1.7 Tbps. Attacks like this aim to overwhelm targets with too much traffic, causing a site or service to go offline.

VPN Deals: Lifetime license for $16, monthly plans at $1 & more

While the attack’s bandwidth of 2.4 Tbps was the largest on record, it fell short of what Azure’s DDoS protections could handle. “Azure’s DDoS protection platform, built on distributed DDoS detection and mitigation pipelines, can absorb tens of terabits of DDoS attacks,” explains Microsoft. “This aggregated distributed mitigation capacity can massively scale to absorb the highest volume of DDoS threats, providing our customers the protection they need.”

Microsoft states that the targeted customer did not experience any impact or downtime. An attack of this caliber could cause significant financial damage and other issues if successful.

“The attack traffic originated from approximately 70,000 sources and from multiple countries in the Asia-Pacific region, such as Malaysia, Vietnam, Taiwan, Japan, and China, as well as from the United States,” explains Microsoft’s Amir Dahan, senior program manager, Azure networking.

The previous largest mitigated DDoS attack reached a peak of 2.3 Tbps and was stopped by Amazon Web Services in June 2020 (via The Verge).

We may earn a commission for purchases using our links. Learn more.

Leave a Reply

Your email address will not be published. Required fields are marked *