News for hackers. Stuff that matters.
Re:Cloudflare outage on November 18, 2025 post mortem by NicoJuicy on Wednesday November 19, 2025 @03:38AM (#45977178)
I think defence against a DDOS against your network is the best reason for a quick rollout
Re:Cloudflare outage on November 18, 2025 post mortem by jabl on Wednesday November 19, 2025 @03:49AM (#45977250)
Maybe, but in that case maybe have some special casing logic to detect that yes indeed we're under a massive DDOS at this very moment, do a rapid rollout of this thing that will mitigate said DDOS. Otherwise use the default slower one?

Of course, this is all so easy to say after the fact..

Re:Cloudflare outage on November 18, 2025 post mortem by xp84 on Wednesday November 19, 2025 @04:14AM (#45977445)
Isn’t CF under a ‘massive DDOS’ 24/7 pretty much by definition? When does malicious traffic rest, and how many targets of same aren’t using CF?
Re:Cloudflare outage on November 18, 2025 post mortem by NicoJuicy on Wednesday November 19, 2025 @04:54AM (#45977722)
It's literally in the blog post as well

> In the internal incident chat room, we were concerned that this might be the continuation of the recent spate of high volume Aisuru DDoS attacks:

Re:Cloudflare outage on November 18, 2025 post mortem by matteocontrini on Wednesday November 19, 2025 @05:20AM (#45977873)
This was not about DDoS defense but the Bot Management feature, which is a paid Enterprise-only feature not enabled by default to block automated requests regardless of whether an attack is going on.

https://developers.cloudflare.com/bots/get-started/bot-manag...

Re:Cloudflare outage on November 18, 2025 post mortem by inemesitaffia on Wednesday November 19, 2025 @05:32AM (#45977940)
So if you didn't enable it your stuff would work?
Re:Cloudflare outage on November 18, 2025 post mortem by matteocontrini on Wednesday November 19, 2025 @05:39AM (#45977984)
It would still fail if you were unluckily on the new proxy (it's not very clear why if the feature was not enabled, indeed):

> Unrelated to this incident, we were and are currently migrating our customer traffic to a new version of our proxy service, internally known as FL2. Both versions were affected by the issue, although the impact observed was different.

> Customers deployed on the new FL2 proxy engine, observed HTTP 5xx errors. Customers on our old proxy engine, known as FL, did not see errors, but bot scores were not generated correctly, resulting in all traffic receiving a bot score of zero. Customers that had rules deployed to block bots would have seen large numbers of false positives. Customers who were not using our bot score in their rules did not see any impact.

Re:Cloudflare outage on November 18, 2025 post mortem by nijave on Wednesday November 19, 2025 @12:28PM (#45982233)
Bots can also cause a DoS/DDoS. We use the feature to restrict certain AI scraper tools by user agent that adversly impact performance (they have a tendency to hammer "export all the data" endpoints much more than regular users do)