←back to thread

How Cloudflare blocked a monumental 7.3 Tbps DDoS attack

(blog.cloudflare.com)
265 points methuselah_in | 3 comments | 20 Jun 25 18:34 UTC | HN request time: 0.405s | source
Show context
password4321 ◴[20 Jun 25 19:34 UTC] No.44331180[source]▶
← Inserting standard complaint about Cloudflare protecting the sites selling these DDoS attacks here (at best: a conflict of interest selling the cure while protecting the disease).
replies(1): >>44373811 #
1. jonathanlydall ◴[25 Jun 25 05:14 UTC] No.44373811[source]▶
How does CloudFlare protect the disease?

Also worth noting that the article specifically mentions how owners of ASNs can subscribe to CloudFlare at no charge to get notified when devices on their network are participating in attacks like this.

replies(2): >>44377538 #>>44398768 #
2. Spivak ◴[25 Jun 25 14:08 UTC] No.44377538[source]▶
I think by treating the symptom they end up making it so that people don't actually do anything of substance in response to these absolutely massive attacks. Just put your site behind Cloudflare, obviously. Problems solved. Why do we need to do anything else?
3. password4321 ◴[27 Jun 25 17:46 UTC] No.44398768[source]▶
> Cloudflare protect[s] the sites selling these DDoS attacks

Not a new problem per https://krebsonsecurity.com/2014/02/the-new-normal-200-400-g...

a funny thing happens when you decide to operate a DDoS-for-hire Web service: Your service becomes the target of attacks from competing DDoS-for-hire services. Hence, a majority of these services have chosen to avail themselves of Cloudflare’s free content distribution service