/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Cloudflare says it mitigated a record-breaking 7.3Tbps DDoS attack in mid-May, which delivered 37.4TB of junk traffic to the target in just 45 seconds

Large-scale attacks designed to bring down Internet services by sending them more traffic than they can process keep getting bigger …

Ars Technica Dan Goodin

Context & Ripple Effects

Cloudflare’s disclosed attack ceilings have risen from a 17.2M-request-per-second financial-sector attack in 2021 through record HTTPS events in 2022. The May incident shifts the comparison from request-rate records to the raw bandwidth a target must absorb.

It also follows Cloudflare’s report that it blocked 20.5 million DDoS attacks in Q1 2025 and saw a 4.8 billion-packets-per-second peak in Q2, suggesting attackers are scaling both volume and packet intensity rather than relying on one metric.

First-order effects

  • The targeted service avoided an outage through Cloudflare’s mitigation capacity, while the incident establishes a substantially higher publicly disclosed bandwidth benchmark for defenders.
  • Organizations without comparable upstream scrubbing or CDN protection must reassess whether their network links and incident plans can withstand short, extreme traffic bursts.

Second-order effects

  • DDoS-protection providers and network operators face pressure to demonstrate headroom, rapid detection, and automated mitigation at multi-terabit scale; customers may scrutinize limits and failover terms more closely.
  • Attackers can use increasingly brief, high-volume bursts to test defenses and disrupt smaller targets, pushing more mitigation traffic and associated costs toward edge-security providers.

Third-order effects

  • If attack size continues to compound, DDoS resilience will become less a capability enterprises build locally and more a core advantage of globally distributed edge networks with large spare capacity.
  • The widening gap between the largest attacks and ordinary organizations’ connectivity could concentrate security dependence among a small set of network-edge providers, though disclosed records alone do not show how broadly such attacks can be sustained.

The trend: DDoS defense is becoming an edge-scale capacity race in which attack traffic grows faster than most individual organizations can economically absorb.

Discussion

  • @eastdakota Matthew Prince on x
    Amused that the first time I heard about this is when reading this post. So cool to have an infrastructure design where even massive attacks like this are no big deal.
  • r/CloudFlare r on reddit
    Massive 7.3 Tbps DDoS Attack Delivers 37.4 TB in 45 Seconds
  • r/technews r on reddit
    Record DDoS pummels site with once-unimaginable 7.3Tbps of junk traffic |  Attacker rained down the equivalent of 9,300 full-length HD movies in just 45 seconds.
  • r/technology r on reddit
    Record DDoS pummels site with once-unimaginable 7.3Tbps of junk traffic |  Attacker rained down the equivalent of 9,300 full-length HD movies in just 45 seconds.