Cloudflare
Reddit take
AI summary of the Reddit excerpts below — not a quote
Cloudflare is a cornerstone of modern web infrastructure, praised for its developer-friendly tools, robust DNS management, and industry-leading post-incident technical analyses. However, recent sentiment is heavily impacted by significant service outages that have highlighted the 'centralization risk' of the platform. While users appreciate the cost-effective domain registration and powerful security features like bot management, there is growing frustration regarding customer support quality and the potential for account lockouts.
Pros
- Exceptional post-incident technical writeups and transparency.
- Developer-friendly deployment for frameworks like Astro and static sites.
- Highly effective bot management and request filtering capabilities.
- Competitive pricing for domain registration compared to traditional registrars.
- Useful tools for homelab enthusiasts, such as Cloudflare Tunnels for secure access.
Cons
- Significant reliability concerns following multiple high-profile outages.
- Customer support is frequently described as slow or unresponsive.
- Risk of 'centralization' where a single provider failure impacts a vast portion of the internet.
- Potential for account or domain lockouts that are difficult to resolve.
Caveats
- Using Cloudflare Tunnels for homelab access creates a dependency where local services become inaccessible if Cloudflare is down.
- Bot management logic has occasionally 'failed closed,' causing outages rather than preventing them.
- Some users suggest keeping domain registration separate from DNS management to mitigate lockout risks.
Best for
- Web developers seeking easy deployment for static sites and modern frameworks.
- Homelab users needing remote access without opening firewall ports.
- Businesses requiring deep insights into web traffic and advanced DDoS protection.
Avoid if
- You require immediate, high-touch human support for critical issues.
- Your architecture cannot tolerate a single point of failure for global DNS and CDN services.
- You prefer to diversify your infrastructure providers to avoid 'eggs in one basket' risks.
This summary uses balanced time weighting with about a 6-month half-life. The evidence is older (median age ~297 days), and because Cloudflare is a fast-changing service where recent outages heavily influence sentiment, the confidence is medium.
Sentiment
25 positive (46%) · 6 mixed (11%) · 23 negative (43%)
Trust + time weighted score: -4% · raw score 4%
What redditors said (10 of 54)
Went with Astro deployed to Cloudflare and immensely appreciated that I was mostly able to stick to just writing plain ol' vanilla HTML, CSS, and JS for the whole thing.
If you do (or use ngrok/cloudflare/tailscale...), run a WAF.
A while back I switched my local resolver on my firewall to use DOT with cloudflare instead of just the regular UDP dns to cloudflare. I have not once felt the effects of their DNS issues. I think they have different infra for it and seem to manage it better.
I guess it's fine that they keep things up and running 97% of the time, but man when it rains it pours.
cloudflare tried to protect us from the cve and caused a bigger outage than the vuln itself lmao
Cloudflare has zero scheduled downtime. Why would anyone use a CDN that intentionally goes down?
Yeah, our company implemented CF as a knee jerk reaction several years ago, no care for redundancy or resiliency.
The Cloudflare centralization risk is no longer theoretical. It’s time to talk about "Eggs in One Basket." We are watching half the internet go dark again today (Dec 5), barely a few weeks after the November 18th outage. 20% of the web went down because of a single bug in their Bot Management logic that "failed closed."
My npm install failed with 500 and I knew cloudfare fcked up again.
it happens, but cloudflare has had multiple outages in the past few weeks, which is frankly unacceptable.
Compare
Cloudflare vs Google DriveCloudflare vs Microsoft AzureCloudflare vs Secureframe