Do not put your site behind Cloudflare if you don't need to

#1

Post by huijzer » Tue, Nov 18, 2025, 12:54 PM UTC

Related: Cloudflare Global Network experiencing issues - https://news.ycombinator.com/item?id=45963780

Do not put your site behind Cloudflare if you don't need to
huijzer.xyz

Re: Do not put your site behind Cloudflare if you don't need to

#2

Post by thejazzman » Tue, Nov 18, 2025, 2:24 PM UTC

I think the big error here is thinking cloud flare is DDoS when it’s an entire self contained platform with workers and pages etc..

You’d see those same errors if someone took their own site down while working on it , probably accidentally

Re: Do not put your site behind Cloudflare if you don't need to

#3

Post by zikero » Tue, Nov 18, 2025, 2:26 PM UTC

If we're talking about putting static assets (like basic websites) on their CDN, or moving your backend to Workers, (etc...) you are by definition moving _away_ from single point-of-failure.

> Maybe that's the core of this message. Face your fears. Put your service on the internet. Maybe it goes down, but at least not by yet another Cloudflare outage.

Well I'd rather have my website going down (along with half the internet) be the concern of a billion dollar corporation with thousands of engineers - than mine.

Re: Do not put your site behind Cloudflare if you don't need to

#4

Post by MallocVoidstar » Tue, Nov 18, 2025, 2:27 PM UTC

> As they say in security, "no one will burn a zero day on you!". For your small blog with one hundred visitors per month, it's probably the same: "no one will burn their DDoS capabilities on you!"

The last I saw you can hire DDoS as a service for like $5 for a short DDoS, and many hosts will terminate clients who get DDoSed.

Re: Do not put your site behind Cloudflare if you don't need to

#5

Post by arend321 » Tue, Nov 18, 2025, 2:28 PM UTC

I'm waiting for my first DDoS attack at which point I will hide behind Cloudflare. I have all the bits in place to make that a smooth transition but would hate every aspect of it.

Re: Do not put your site behind Cloudflare if you don't need to

#6

Post by xacky » Tue, Nov 18, 2025, 2:28 PM UTC

I don't consider Cloudflare part of the "real" internet anymore, instead it's a private intranet that got too big.

Re: Do not put your site behind Cloudflare if you don't need to

#7

Post by mariopt » Tue, Nov 18, 2025, 2:31 PM UTC

Enterprise self hosting is an expensive nightmare for most companies. I think it is time to discuss multi cloud deployments to escape outages.

I am hosted on Cloudflare but my stack is also capable of running on a single server if needed, most libraries are not design with this in mind.

I’m also wondering if all these recent outages are connected to cyber attacks, the timing is strange.

Re: Do not put your site behind Cloudflare if you don't need to

#8

Post by neya » Tue, Nov 18, 2025, 2:31 PM UTC

The lesson I learned is it's OK to put your site with Cloudflare. It's not ok to put your DNS on a registrar who is also on Cloudflare. We got locked out because our registrar is also on Cloudlfare, and now I can't even switch DNS to get the site back up. Keep your domain name registrar, DNS service provider and application infrastructure provider separately.

Re: Do not put your site behind Cloudflare if you don't need to

#9

Post by thoroughburro » Tue, Nov 18, 2025, 2:31 PM UTC

[flagged]

Re: Do not put your site behind Cloudflare if you don't need to

#10

Post by fionic » Tue, Nov 18, 2025, 2:32 PM UTC

Cloudflare tunnels makes it dead simple these days. Like some others in the comments it seems; I'd rather Cloudflare fighting the war against hacker armies than me. Once our networks become compromised from opening our firewalls (possibly even not) our routers and IOT devices become unwillingly complicit in the army that's bringing the internet down.