The docs subdomain received 100,000 hits yesterday. The bugs subdomain received nearly 700,000 hits yesterday. Bots are totally out of control here.

Putting Cloudflare in front of the wiki is a possibility. But that's a huge pain because Cloudflare demands full control of DNS for free accounts.

I checked with our host and they only offer mod_security, which is not going to fix this.

Looking at our current DNS provider next for solutions.

In the meantime, I've disabled anonymous access to the bug tracker and anonymous access to most of the Special pages in the wiki. I also added an Apache rule to block two of the Microsoft cloud servers that are responsible for most of the traffic.

Over the past 12 hours I was able to stop the wiki attack with server configuration changes.

We are seeing less traffic from Microsoft after reaching out to their Security Response Center. However, the DDoS against the bugs subdomain continues to represent millions of unique bots that are not slowing down overall. Changes to our DNS and edge design are underway.

Quote: Originally posted by miqrogroove

Putting Cloudflare in front of the wiki is a possibility. But that's a huge pain because Cloudflare demands full control of DNS for free accounts.

Clownflare's "Just a moment..." pages also really don't like you having certain functionality unavailable in the browser.

Is there not a way to intentionally throttle such bot traffic if they exceed a certain amount of requests? I'm assuming it's AI scrapers and the like.

I'm not even anti-AI, I just wish it had some kind of respect for smaller servers like ours.

When it comes to DDoS attacks, the only options are edge solutions or public lockdowns. This attack lasted several days and only showed signs of slowing in the past couple hours. With the bug tracker content now hidden behind the login, hopefully that will discourage future attacks.