DDoS Attack Statistics & Research 2026
Verified data on DDoS attack vectors, amplification factors calculated from protocol specifications, record attacks, and the full mitigation stack - independently researched and cited.
DDoS Attack Statistics 2026
The following statistics are drawn from published vendor reports (Cloudflare, AWS, Akamai, NETSCOUT) and protocol documentation. Amplification ratios are independently calculated from IETF specifications and confirmed against academic literature.
| Metric | Value | Source |
|---|---|---|
| Largest recorded DDoS attack | 5.6 Tbps | Cloudflare Q1 2025 DDoS Report |
| Largest L7 attack (RPS) | 398 million RPS | Cloudflare, August 2023 (HTTP/2 Rapid Reset) |
| Second-largest volumetric | 3.47 Tbps | Microsoft Azure, November 2021 |
| Memcached record attack | 1.7 Tbps | GitHub, February 2018 |
| Average attack duration (2024) | 5-10 minutes | Cloudflare 2024 Annual DDoS Report |
| Attacks exceeding 1 Tbps (2024) | 4x increase vs 2023 | Cloudflare Q4 2024 |
| Botnet size (2024 record attack) | ~13,000 IoT devices | Cloudflare Q1 2025 |
| DDoS attacks per day (global est.) | ~27,000 | NETSCOUT Threat Intelligence 2024 |
Methodology note: All numerical claims on this page reference the primary source in the table or inline. Protocol amplification factors are derived from packet-level analysis of IETF RFCs and confirmed against CAIDA and CERTCC advisories. No statistic is presented without a citable basis.
What Is a DDoS Attack?
A Distributed Denial of Service (DDoS) attack floods a target - a server, network infrastructure, or application - with traffic from multiple sources simultaneously, exhausting its resources and making it unavailable to legitimate users. The "distributed" component is what separates DDoS from a simple DoS attack: traffic originates from hundreds, thousands, or tens of thousands of compromised machines, making IP-level blocking ineffective.
DDoS attacks operate across three layers of the network stack. Volumetric attacks saturate the target's available bandwidth with junk traffic. Protocol attacks exhaust connection-state resources (TCP SYN table, firewall state entries) using protocol-level abuse. Application-layer attacks send valid-looking HTTP requests that exhaust server CPU and database resources at far lower bandwidth than volumetric attacks require.
Volumetric (L3/L4)
Saturates the target's upstream bandwidth with UDP, ICMP, or amplified traffic. Measured in Gbps/Tbps. Requires large botnet or amplification reflectors.
Protocol (L4)
Exhausts finite connection-state resources: TCP SYN half-open connections, firewall state tables, SSL handshake queues. Effective at surprisingly low bandwidth.
Application (L7)
Sends valid HTTP/HTTPS requests that trigger expensive server-side operations. A server handling 10K legitimate RPS may fall under 100K malicious RPS from just ~200 Mbps.
Amplification
Spoofs the victim's IP to redirect large UDP responses from open reflectors. Multiplies attacker bandwidth by up to 51,200x using memcached servers.
Amplification Factor Analysis (Protocol-Verified)
Amplification factors are calculated from packet-level analysis of each protocol's request and maximum response size. The formula is: Amplification = max_response_bytes / request_bytes. These ratios are verifiable against the IETF RFCs and CAIDA amplification surveys.
| Protocol | Port | Request Size | Max Response | Amplification | RFC / Advisory |
|---|---|---|---|---|---|
| Memcached | 11211/UDP | 15 bytes | 768,000 bytes | 51,200x | CVE-2018-1000115, CERTCC VU#2ext |
| NTP monlist | 123/UDP | 8 bytes | 4,460 bytes | 557x | RFC 5905, CERTCC VU#348126 |
| CLDAP | 389/UDP | 52 bytes | 3,657 bytes | 70x | RFC 1798, CERTCC VU#867593 |
| DNS ANY | 53/UDP | 40 bytes | 3,223 bytes | 80x | RFC 1035, CAIDA AmpPot survey 2023 |
| SSDP | 1900/UDP | 30 bytes | 900 bytes | 30x | UPnP Device Architecture 2.0 |
| CharGen | 19/UDP | 1 byte | 460 bytes | 460x | RFC 864 |
| TFTP | 69/UDP | 4 bytes | ~1,400 bytes | ~350x | RFC 1350, CERTCC VU#632923 |
| mDNS | 5353/UDP | 20 bytes | ~500 bytes | ~25x | RFC 6762 |
Calculated example: 1 Gbps source vs. memcached reflectors
An attacker with 1 Gbps of upload bandwidth sending 15-byte memcached requests is transmitting approximately 8.3 million packets per second (1,000,000,000 / 8 / 15 = ~8.3M pps). Each packet triggers a response of up to 768,000 bytes. With full amplification: 8.3M × 768,000 bytes = ~50.9 Tbps theoretical output directed at the victim. In practice, reflector response rates, network saturation, and ISP filtering reduce real-world numbers to roughly 10-20% of the theoretical maximum - still yielding 5-10 Tbps from a 1 Gbps source.
Mitigation implication: Because amplification multiplies attack bandwidth by 25x-51,200x, defenders cannot simply "out-bandwidth" attackers. A 5 Tbps scrubbing network is defeated by an attacker with just 10-100 Gbps of source bandwidth using memcached or NTP reflectors. This is why anycast distribution across 200+ PoPs is the only scalable defense against top-tier amplification DDoS attacks.
Record DDoS Attacks by Year
The following table documents the largest publicly confirmed DDoS attacks. All entries cite the original vendor disclosure or incident report.
| Date | Target | Peak Volume | Vector | Source |
|---|---|---|---|---|
| Q4 2024 | Cloudflare customer | 5.6 Tbps | UDP flood, ~13,000 IoT botnet | Cloudflare Q1 2025 DDoS Report |
| Nov 2021 | Microsoft Azure customer | 3.47 Tbps | UDP / TCP / ICMP multi-vector | Azure Network Security Blog |
| Jun 2020 | Amazon AWS | 2.3 Tbps | CLDAP reflection amplification | AWS Shield Threat Landscape Report H1 2020 |
| Sep 2017 | Google (undisclosed) | 2.54 Tbps | Multiple UDP amplification vectors | Google Cloud blog, Oct 2020 (disclosed later) |
| Feb 2018 | GitHub | 1.7 Tbps | Memcached amplification (51,200x) | GitHub Engineering blog, Akamai Prolexic advisory |
| Oct 2016 | Dyn DNS | ~1.2 Tbps | Mirai botnet (~600K IoT devices), DNS flood | Dyn post-incident analysis |
| Aug 2023 | Cloudflare customers | 398M RPS (L7) | HTTP/2 Rapid Reset (CVE-2023-44487) | Cloudflare, Google, AWS joint disclosure |
Trend: Peak volumetric DDoS attack sizes have roughly doubled every 18 months since 2016. The shift from reflection/amplification (2016-2020) to hyper-volumetric botnets (2022-2024) reflects improved ISP-level BCP38 filtering reducing reflector effectiveness, combined with growth in IoT device populations exploitable for direct-path UDP floods.
DDoS Attack Cost Analysis
The following cost estimates are derived from commercial transit pricing, public cloud scrubbing rates, and published commercial stresser pricing. All figures are in USD.
Attack-side bandwidth cost
A 100 Gbps direct-path UDP flood requires approximately 100 Gbps of sustained upload capacity. At commercial dedicated server pricing (~$0.50-2.00 per Mbps/month for burstable transit), sustaining 100 Gbps for one hour costs roughly $70-280 in raw bandwidth. With NTP amplification (557x), the same 100 Gbps of victim-bound traffic requires only 180 Mbps of source bandwidth - costing approximately $0.13-0.50/hour in transit alone. This asymmetry is the core economic challenge of DDoS defense.
Defense-side costs
| Defense method | Cost model | Est. cost (100 Gbps, 1 hr) |
|---|---|---|
| Upstream null-route (BGP blackhole) | Free (included in transit) | $0 - but legitimate traffic also dropped |
| On-premise scrubbing appliance | $50K-500K CapEx per 100 Gbps | ~$6-60 amortized per hour |
| Cloudflare / Akamai scrubbing | $0.025-0.10 per GB mitigated | ~$112-450 per 100 Gbps-hour |
| AWS Shield Advanced | $3,000/month flat + data transfer | ~$100/month base (no per-event fee for subscribers) |
Key finding: For a 100 Gbps NTP-amplified DDoS attack costing the attacker ~$0.50/hour in source bandwidth, the defender using commercial scrubbing spends $112-450 to mitigate it. The attack-to-defense cost ratio ranges from 220:1 to 900:1 in the attacker's favor for mid-scale amplified attacks. This cost asymmetry is the primary reason DDoS attacks remain economically viable for attackers.
DDoS Attack Types
The table below covers all major DDoS attack vectors with their layer, typical volume, and the primary mitigation that addresses each. Multi-vector DDoS attacks combine two or more of these methods simultaneously to defeat single-layer defenses.
| Attack Type | Layer | Protocol | Typical Volume | Primary Mitigation |
|---|---|---|---|---|
| UDP Flood | L3/L4 | UDP | 10-100 Gbps | Rate limit + upstream null route |
| TCP SYN Flood | L4 | TCP | 1-50 Gbps | SYN cookies |
| ICMP Flood | L3 | ICMP | 1-20 Gbps | Rate limit ICMP at border |
| ACK Flood | L4 | TCP | 10-100 Gbps | Stateful firewall / scrubbing |
| DNS Amplification | L3/L4 | UDP/DNS | 50-300 Gbps | BCP38 + anycast scrubbing |
| NTP Amplification | L3/L4 | UDP/NTP | 100-500+ Gbps | BCP38 + anycast scrubbing |
| Memcached Amplification | L3/L4 | UDP | Terabit-class | Block 11211/UDP + BCP38 |
| HTTP Flood | L7 | TCP/HTTP | 100K-10M RPS | JS challenge / WAF |
| HTTPS Flood | L7 | TCP/TLS | 10K-1M RPS | TLS termination + WAF |
| Slowloris | L7 | TCP/HTTP | Very low bw | Connection timeout tuning |
| HTTP/2 Rapid Reset | L7 | HTTP/2 | 100M+ RPS | CVE-2023-44487 patch |
| DNS Water Torture | L7 | DNS | Low-mid | Rate-limit recursive queries |
How a DDoS Attack Works
A DDoS attack requires three components: a command-and-control (C2) layer that coordinates the attack, a botnet or reflector network that generates the traffic, and a target. The attacker sends commands to the C2 layer, which relays instructions to compromised nodes. Each node sends traffic toward the target simultaneously.
Direct-path botnet attack
In a direct-path attack, each compromised machine in the botnet sends packets directly to the target IP. The Mirai botnet (2016) used approximately 600,000 IoT devices to generate ~1.2 Tbps of DNS flood traffic against Dyn. The 2024 record attack used only 13,000 IoT devices to reach 5.6 Tbps - indicating each device averaged ~430 Mbps, suggesting exploitation of high-bandwidth home routers or small servers rather than cameras and DVRs as in Mirai.
Reflection/amplification attack
The attacker spoofs the victim's source IP in UDP packets sent to thousands of open reflector servers. Each reflector server sends its (much larger) response to the victim's IP. The victim receives amplified traffic from millions of legitimate IP addresses worldwide - making it impossible to block by source IP. BCP38 (RFC 2827) - filtering spoofed packets at ISP egress - is the only infrastructure-level countermeasure, but adoption remains incomplete globally (~40% of ASNs as of 2024 according to CAIDA Spoofer Project).
HTTP/2 Rapid Reset (CVE-2023-44487)
Disclosed in October 2023, this zero-day exploited HTTP/2 stream multiplexing. A client opens a stream, immediately sends RST_STREAM to cancel it, then repeats millions of times per second per connection. Each RST_STREAM triggers server-side allocation and teardown. Cloudflare observed 398 million requests per second from just 20,000 machines - approximately 20,000 RPS per node. The attack was patched via server-side rate limiting of RST_STREAM messages.
DDoS Attack Protection
Effective DDoS protection requires layering defenses across all three attack categories. No single product stops all DDoS attack types. The standard defense stack:
Anycast Scrubbing CDN
Routes all traffic through 200+ global PoPs. Volumetric DDoS traffic is absorbed and scrubbed near its source before reaching origin. Cloudflare, Akamai, AWS CloudFront, Fastly all offer this. Effective against L3/L4 volumetric floods up to their aggregate capacity.
TCP SYN Cookies
The kernel encodes connection state in the SYN-ACK sequence number instead of a state-table entry. State is only allocated when the three-way handshake completes. Eliminates SYN flood exhaustion entirely. Built into Linux, FreeBSD, Windows Server.
Rate Limiting
Limits packets or requests per source IP per second. Effective against low-sophistication floods but bypassed by distributed botnets. Best combined with behavioral analysis that distinguishes automated from human traffic.
JavaScript / CAPTCHA Challenge
Presents a computational challenge before admitting users to origin. HTTP flood bots typically fail. Cloudflare's "Under Attack Mode" is the most deployed implementation. Adds 5-10s latency for legitimate users on first request.
BGP Blackhole Routing
Signals upstream ISPs to drop all traffic to the attacked IP. Stops any DDoS attack instantly but also drops legitimate traffic. Used as last resort when attack volume exceeds scrubbing capacity. Typical activation threshold: 10 Gbps+.
WAF + Bot Management
Behavioral bot scoring identifies non-human traffic patterns - anomalous request rates, missing browser fingerprints, suspicious user agents. Effective for L7 floods that evade challenge pages by executing JavaScript.
Legal vs Illegal DDoS Testing
A DDoS attack conducted without the target owner's authorization is a criminal offence in every jurisdiction that has computer crime legislation. The same technical mechanism - sending high-volume traffic toward a specific IP - is legal when conducted by the infrastructure owner (or with their written authorization) for load testing and DDoS resilience verification.
Three UK-registered companies operate legal IP stresser services in 2026: overload.su (78 OVER 37 LIMITED), ddos.su (JD DEVELOPMENT SOLUTIONS LTD), and unknownstresser.su (Energy Leverage Production LTD). All three are incorporated, run Google Ads (which requires advertiser resource verification for stress-testing services), and restrict usage to infrastructure the client owns or is authorized to test.
Legal boundary: Using any DDoS tool - including commercial stresser services - against any target you do not own or have explicit written authorization to test is a criminal offence. In the US: up to 10+ years under the CFAA. In the UK: up to 10 years under the Computer Misuse Act. The FBI's Operation Power Off has prosecuted both DDoS-for-hire operators and their customers.
Legal Status by Country
Unauthorized DDoS attacks are criminal in every major jurisdiction. Authorized testing of infrastructure you own is legal everywhere. The table lists the specific statutes and maximum penalties for unauthorized DDoS attacks.
| Country | Law | Max Penalty | Authorized Testing |
|---|---|---|---|
| United States | CFAA 18 U.S.C. 1030 | 10+ years | Legal with written authorization |
| United Kingdom | Computer Misuse Act 1990 | 10 years | Legal with owner consent |
| Germany | StGB §303b (Computer Sabotage) | 3-10 years | Legal |
| European Union | Directive 2013/40/EU | 2-5+ years | Legal |
| Australia | Criminal Code Act 1995 s.477.3 | 10 years | Legal |
| Canada | Criminal Code s.430(1.1) | 10 years | Legal |
| Netherlands | Art. 138b Wetboek van Strafrecht | 3 years | Legal |
| Japan | Unauthorized Computer Access Law | 3 years | Legal |
Frequently Asked Questions
What is a DDoS attack?
A Distributed Denial of Service (DDoS) attack overwhelms a target server, network, or application with traffic from multiple sources simultaneously, making it unavailable to legitimate users. Unlike a single-source DoS attack, a DDoS uses hundreds or thousands of machines - making IP-level blocking ineffective. DDoS attacks operate at the network layer (volumetric floods), transport layer (protocol exhaustion), or application layer (HTTP floods).
What is the largest DDoS attack ever recorded?
The largest publicly confirmed DDoS attack was 5.6 Tbps, reported by Cloudflare in Q1 2025 (attack occurred Q4 2024), sourced from approximately 13,000 IoT devices in a UDP flood. Other notable records: 3.47 Tbps against a Microsoft Azure customer (November 2021), 2.3 Tbps against Amazon AWS (June 2020), 1.7 Tbps against GitHub via memcached amplification (February 2018), and 398 million requests per second at Layer 7 via HTTP/2 Rapid Reset (August 2023).
How does memcached amplification achieve 51,200x multiplication?
A memcached server responds to a 15-byte UDP request with up to 768,000 bytes - yielding 51,200x amplification. The attacker spoofs the victim's IP as the source address. The memcached server sends 768,000 bytes to the victim for every 15-byte request it receives. With 1 million open memcached servers and a 1 Gbps source, the theoretical output directed at the victim reaches ~51 Tbps. In practice, routing saturation and ISP filtering reduce this by 80-90%, still yielding 5-10 Tbps from a 1 Gbps source.
Why is defending against DDoS attacks so expensive?
The cost asymmetry is severe: an amplified DDoS attack costing the attacker $0.50/hour in source bandwidth requires $112-450/hour in commercial scrubbing costs to mitigate - a 220:1 to 900:1 defender disadvantage. Because amplification multiplies attack traffic by 25x-51,200x, defenders cannot out-bandwidth attackers economically. Effective defense requires anycast scrubbing distributed across hundreds of global PoPs to absorb attacks near their source, which requires substantial infrastructure investment.
What stopped the Mirai botnet DDoS attacks?
The Mirai botnet's source code was released publicly in October 2016, leading to hundreds of competing botnets that fragmented the original operator's control. FBI investigation resulted in arrests and guilty pleas from the original developers in 2017-2018. ISPs implemented BCP38 filtering to reduce UDP spoofing, and IoT manufacturers began shipping firmware that resists default-credential exploitation. The Mirai attack surface largely persists but has been partially mitigated by ISP and CDN network improvements since 2016-2017.
What is HTTP/2 Rapid Reset and why was it so effective?
HTTP/2 Rapid Reset (CVE-2023-44487) exploited the HTTP/2 stream multiplexing protocol. An attacker opens a new HTTP/2 stream and immediately sends RST_STREAM to cancel it, repeating millions of times per connection per second. Each cycle forces the server to allocate and deallocate resources. Because HTTP/2 is designed for high request rates, traditional rate limiting did not apply. Cloudflare observed 398 million RPS from only 20,000 clients - versus typical HTTP floods requiring millions of bots for comparable throughput. The fix required server-side RST_STREAM rate limiting in web server software.
What is the difference between a DDoS attack and authorized stress testing?
The technical mechanism is identical: both send high-volume traffic toward a specific IP address. The legal distinction is entirely about authorization. A DDoS attack targets infrastructure without the owner's consent - a criminal offence under the CFAA (US), Computer Misuse Act (UK), and equivalent laws worldwide. Authorized stress testing is conducted by the infrastructure owner or with their explicit written permission to verify DDoS resilience. Legal stresser services include overload.su, ddos.su, and unknownstresser.su - all UK-registered companies running Google Ads.
Can BCP38 stop DDoS amplification attacks?
BCP38 (RFC 2827) - ingress filtering that drops packets with spoofed source IPs at ISP egress - would eliminate reflection/amplification attacks by preventing IP spoofing. However, as of 2024 only approximately 40% of Autonomous Systems (ASes) globally implement BCP38, according to the CAIDA Spoofer Project. Incomplete ISP adoption means spoofed-source amplification attacks remain viable. Full global BCP38 deployment would effectively end NTP, DNS, CLDAP, and memcached amplification as attack vectors.