11–20 of 34 posts
We would people try to do a ddos on them. A ddos is a temporary thing. Only time it is worth it do do a ddos is when there is some kind of event thing. Like if some one wants to get a site down today so people can't vote. And cloudflare does not really have anything like that. Their customers yes, them no.
The same reason anyone ever DDOSes anything: because they're assholes.
Edit: Appears so, as the post finally went through.
I would kill for a Null Route REST API at peering points/network upstream providers.
Routers shouldn't speak HTTP. People who don't know how to use blackhole communities have no business controlling them.
This is why most CDNs avoid taking on controversial customers like 4chan, kaddafi.hk and other sites trafficking in illegal content. Due to their decision to accept anyone, Cloudflare is a constant target for DDOS attacks and their legitimate users occasionally share the brunt of those attacks.
CloudFlare, a product supposed to increase uptime, has been my product's only source of downtime for the past several months.
This is why most CDNs avoid taking on controversial customers like 4chan, kaddafi.hk and other sites trafficking in illegal content. Due to their decision to accept anyone, Cloudflare is a constant target for DDOS attacks and their legitimate users occasionally share the brunt of those attacks.
What bothers me is that our CDN gets a lot of downtime whenever CloudFire gets hit. They're totally separate services, or at least they should be, but I always know to watch out when I see articles like these.
They manage so much stuff that any downtime they have will make a lot of people unhappy. It already happened once (http://oneurl.me/cloudflare-broke-the-internet)