could you expand on that? What exactly is preventing you from proxying your blog through cloudflare?

You're not processing customer data there are you?

No Cloudflare specialist, isn't Cloudflare depending on DNS mappings sending all domain traffic through Cloudflare? How would we send only www.eventsofa.de/blog through Cloudflare?

You could switch to blog.eventsofa.de.

That wouldn't solve today's traffic spike, and there are probably some lower-hanging fruits that should at the very least keep the site online. Anything sold in the last five years with an ethernet port should easily be able to handle a static site even during rare spikes in traffic.

But the Cloudflare DNS configuration isn't something to be scared of: I used to feel similarly nervous when fiddling around with DNS, but haven't had a single problem configuring 20+ sites with Cloudflare. (I would, however, be slightly more nervous about google's reaction to the move to a subdomain this would require.)

Thanks for the long feedback, we have a long tail of content in the blog so we won't migrate to a subdomain. Google says no problem, but we had SEO problems in the past when migrating subdomains although everything done by the book with redirects.

Doesn't work, but the assumption was on that most blogs have a separate subdomain, so that the subdomain could be redirected to cloudflare. That said, if you can't handle a mild HN attack, you should be weary of your DDoS resistance, and consider ways to do more caching in front. It's a lot easier to just tank DDoS traffic than to reject connections based on some guessed measure of whether they are legitimate or evil, and in this case here they are legitimate, so these filters wouldn't work anyway.

Thanks for the feedback, but we do handle our blog different than the rest of our platform, it's low specced and hosted differently, we do not consider the blog essential to our service.