DDoS Protection Mitigation Solutions | Cloudflare DDoS attacks can slow or shut down services, but Cloudflare stops them all With 388 Tbps of network capacity, Cloudflare has mitigated some of the largest DDoS attacks ever recorded, without slowing down performance for customers
Defending the Internet: how Cloudflare blocked a monumental 7 . . . In mid-May 2025, Cloudflare blocked the largest DDoS attack ever recorded: a staggering 7 3 terabits per second (Tbps) This comes shortly after the publication of our DDoS threat report for 2025 Q1 on April 27, 2025, where we highlighted attacks reaching 6 5 Tbps and 4 8 billion packets per second (pps)
Record-Breaking 7. 3 Tbps DDoS Attack Targets Hosting Provider The 7 3 Tbps DDoS attack, seen by Cloudflare in mid-May, lasted only 45 seconds and it was aimed at a hosting provider “Hosting providers and critical Internet infrastructure have increasingly become targets of DDoS attacks,” the web performance and security solutions provider said in a blog post on Thursday
Overview · Cloudflare DDoS Protection docs Cloudflare automatically detects and mitigates distributed denial-of-service (DDoS) attacks via our autonomous DDoS systems These systems include multiple dynamic mitigation rules exposed as DDoS attack protection managed rulesets You can customize the mitigation rules included in these rulesets to optimize and tailor the protection to your
DDoS threat report for 2025 Q1 | Cloudflare Radar In the first quarter of 2025, Cloudflare blocked 20 5 million DDoS attacks That represents a 358% year-over-year (YoY) increase and a 198% quarter-over-quarter (QoQ) increase Around one third of those, 6 6 million, targeted the Cloudflare network infrastructure directly, as part of an 18-day multi-vector attack campaign
Massive 7. 3 Tbps DDoS Attack Delivers 37. 4 TB in 45 Seconds . . . Cloudflare on Thursday said it autonomously blocked the largest distributed denial-of-service (DDoS) attack ever recorded, which hit a peak of 7 3 terabits per second (Tbps) The attack, which was detected in mid-May 2025, targeted an unnamed hosting provider "Hosting providers and critical