65 engineers on Hacker News describe using Cloudflare first-hand: 21 endorse it, 10 regret it, 8 are mixed.
“I used to use cloudflare dns, but the same cloudflare harassed me the entire day testing if I'm a robot.”
regret · personal · likoya · 2026-11-02 · source ↗ · wrong label?“Cloudflare has been pretty reliable so far. I've been using their services since the beginning.”
endorse · personal · alfg · 2026-10-19 · source ↗ · wrong label?“I use the cloudflare ZTNA agent on my work laptop and often run into uncategorized websites.”
regret · production · johnbatch · 2026-10-02 · source ↗ · wrong label?“On Cloudflare, getting an new website up and running with a freshly registered domain takes only a few minutes.”
endorse · production · jillesvangurp · 2026-09-08 · source ↗ · wrong label?“The best MCP servers I use day to day (Cloudflare sticks out) do a really good job of exposing only what an agent might actually want”
endorse · personal · nameless912 · 2026-08-28 · source ↗ · wrong label?“I've been using Cloudflare's ecosystem heavily for my video tools”
endorse · production · charlesding2024 · 2025-12-24 · source ↗ · wrong label?“Riley did the heroic work of caching it all with Cloudflare after waking up to the site being down.”
endorse · production · lukeigel · 2025-12-21 · source ↗ · wrong label?“I wanted to host on Cloudflare but half the stuff doesn't work so I'm forced into Vercel.”
regret · personal · esperent · 2025-12-05 · source ↗ · wrong label?“I'm migrating my customers off Cloudflare. I don't think they can swallow the next botnet attacks”
regret · production · polack · 2025-11-19 · source ↗ · wrong label?“Unfortunately whatever anti-bot magic they have isn't quite having the effect, even after two hours.”
mixed · production · frameset · 2025-11-18 · source ↗ · wrong label?“The first time we switched to Cloudflare which saved us. Even with Cloudflare, the DDoS attempts are still damaging”
endorse · production · the_bear · 2025-11-18 · source ↗ · wrong label?“We’ve moved to Cloudflare and not only is the performance great, but it costs less.”
endorse · production · jonathanlydall · 2025-10-29 · source ↗ · wrong label?“personally I'm a fan of CloudFlare for HTTP load balancing”
endorse · production · adamcharnock · 2024-12-02 · source ↗ · wrong label?“we run cloudflare in front of them to handle frequent DDoS attacks. We also pay for a cloudflare enterprise plan though.”
mixed · production · charrondev · 2023-07-07 · source ↗ · wrong label?“CF we use, and as you said, they are a tool. Plenty of ways they could be better, but they are still the best (in moderate price range) we know.”
mixed · production · bornfreddy · 2022-12-15 · source ↗ · wrong label?“have used cloudflare before, because it's easy to do letsencrypt DNS challenge method with it”
endorse · production · erinaceousjones · 2022-11-29 · source ↗ · wrong label?“DNS performance improved as we switched over to Cloudflare as well. Saw a decrease in bot traffic. No complaints about usability or being blocked.”
endorse · production · hw · 2022-11-19 · source ↗ · wrong label?“We migrated from pro to enterprise cloudflare because the imaging api costs basically put us at the price where upgrading gave us a lot of added benefits”
endorse · production · shmoogy · 2022-01-06 · source ↗ · wrong label?“we just already used Cloudflare for lots of things and like the company”
endorse · production · leesalminen · 2021-12-19 · source ↗ · wrong label?“I've been having this problem a lot recently. First Rackspace, later CloudFlare.”
regret · production · maxk42 · 2021-12-18 · source ↗ · wrong label?“Eventually we migrated behind CF and the problem was solved”
endorse · production · maxgashkov · 2021-11-14 · source ↗ · wrong label?“Sit the Next.js site behind CloudFlare, and then we also don't really pay data transfer costs.”
endorse · production · fbrchps · 2021-09-07 · source ↗ · wrong label?“I think, only the enterprise customers can truly claim benefit of all 200 PoPs... it doesn't match our interaction with Cloudflare's support.”
mixed · production · ignoramous · 2020-11-13 · source ↗ · wrong label?“We've moved off of Cloudflare and had a lot fewer issues. ... it's hard to know exactly what happened when things fail”
regret · production · eis · 2020-07-27 · source ↗ · wrong label?“I'm using Cloudflare, which makes the site a lot faster and greatly reduces load on the webserver.”
endorse · production · it · 2019-09-20 · source ↗ · wrong label?“Delivery of content was faster (eg we moved to Cloudflare).”
endorse · production · AhmedF · 2019-08-14 · source ↗ · wrong label?“it's easy to make a mistake in the Cloudflare DNS web interface, e.g. it's easy to accidentally remove an entry.”
mixed · production · yoran · 2019-06-05 · source ↗ · wrong label?“Cloudflare is fine but they are still an order of magnitude slower, which is why we switched.”
regret · production · tylermenezes · 2019-04-19 · source ↗ · wrong label?“they do support websockets, but at a limited and undisclosed rate (I.e. You don't know how many is too many until they ask you to upgrade your plan).”
regret · production · napsterbr · 2018-11-15 · source ↗ · wrong label?“This reads more of an advert for Cloudflare (we use it and live it)”
endorse · production · victor106 · 2017-11-21 · source ↗ · wrong label?“CloudFlare's DNS was measurably, and consistently, faster than almost every provider we tested... one of the reasons we did so was unreliable lag with DNS updates at CloudFlare.”
mixed · production · thefarseeker · 2017-01-10 · source ↗ · wrong label?“CloudFlare is really the best thing to happen to WordPress since Imgix.”
endorse · production · jawngee · 2016-11-01 · source ↗ · wrong label?“peering with cloudflare lets us save on bandwidth costs!”
endorse · production · 1 yr · jhgg · 2016-02-24 · source ↗ · wrong label?“We switched over the CloudFlare and made that $100/day cost go away. CloudFlare's free service has been amazing and we've had no hiccups with it.”
endorse · production · aagha · 2015-09-10 · source ↗ · wrong label?“We moved off of CloudFlare because of repeated outages and bugs. Our uptime improved significantly without CloudFlare.”
regret · production · crystaln · 2014-12-05 · source ↗ · wrong label?“After moving to CloudFlare, we are not even aware of it if we get hit by a DDos.”
endorse · production · aytekin · 2014-09-27 · source ↗ · wrong label?“we had to do an emergency switch to another CDN because the performance was SOOOOOO bad”
regret · production · blakefrost · 2013-01-05 · source ↗ · wrong label?“I've been using CloudFlare for a site with >20m hits per month.”
mixed · production · fsckin · 2012-12-01 · source ↗ · wrong label?“I've been using CloudFlare on a project and have been mostly very pleased with it.”
mixed · production · erikcw · 2012-11-21 · source ↗ · wrong label?“on a beefy home server+ cloudflare for object storage and video streaming.”
neutral · production · slroger · 2025-12-20 · source ↗ · wrong label?“we resolved this by switching away from Cloudflare handling our DNS to revert it back to our domain service provider”
neutral · production · simonv3 · 2025-09-24 · source ↗ · wrong label?“have to pass a Cloudflare challenge [1].”
neutral · production · jasoncartwright · 2025-08-21 · source ↗ · wrong label?“It's not much different from how we as programmers use things like Cloudflare or AWS Lambda.”
neutral · production · weitendorf · 2024-12-02 · source ↗ · wrong label?“Cloudflare for the smaller services.”
neutral · production · distortionfield · 2024-06-01 · source ↗ · wrong label?“our current marketing site is NextJS hosted on Hetzner fronted by Cloudflare, fortunately that's still up and never has any problems.”
neutral · production · madjam002 · 2023-10-30 · source ↗ · wrong label?“My chosen stack is React (DaisyUI, deployed with cloudflare) + Node”
neutral · personal · lightning19 · 2023-03-11 · source ↗ · wrong label?“We use Cloudflare right now for the CDN, but as mentioned in the blog post”
neutral · production · kiwicopple · 2022-12-13 · source ↗ · wrong label?“We also use Terraform for managing CloudFlare and all sorts of other providers. It has been a dream.”
neutral · production · busterarm · 2020-10-23 · source ↗ · wrong label?“For CDNs we switched from Fastly to Cloudflare because we needed support for SSH (port 22)”
neutral · production · sytse · 2020-10-23 · source ↗ · wrong label?“I work at hCaptcha, we run CF's captcha.”
neutral · production · DrJosiah · 2020-07-20 · source ↗ · wrong label?“The WAF was one of the reasons we switched, our existing provider wanted to charge us 10x more just for the WAF than the entire Cloudflare plan is now.”
neutral · production · lukevp · 2020-03-01 · source ↗ · wrong label?“we've talked to them pretty extensively about the whole project, and even did a case study about our use-case with the bandwidth alliance, and as we switched cloud providers”
neutral · production · CherryJimbo · 2019-04-13 · source ↗ · wrong label?“Am using it with cloudfare's encrypted DNS just as one more middle finger to my ISP.”
neutral · personal · plg · 2018-12-30 · source ↗ · wrong label?“I learned and brought in production the followings: AWS Cloudflare and Lambda (with Go)”
neutral · production · apeacox · 2018-12-23 · source ↗ · wrong label?“as a business we use Cloudflare for DNS”
neutral · production · gtf21 · 2018-11-27 · source ↗ · wrong label?“$20/mo to CloudFlare, and more.”
neutral · production · wild_preference · 2018-11-12 · source ↗ · wrong label?“a free account in cloudflare, code and deploy.”
neutral · personal · mcs_ · 2018-10-04 · source ↗ · wrong label?“there's a large discrepancy between the traffic / visitor count shown by Cloudflare and Matomo”
neutral · production · ThePhysicist · 2018-09-26 · source ↗ · wrong label?“CloudFlare gave us a quote of over $2500/month and Fly.io was free of cost.”
neutral · production · pcx · 2018-04-05 · source ↗ · wrong label?“We use it on https://hsreplay.net, which serves about 100-200k requests / day behind Cloudflare.”
neutral · production · scrollaway · 2016-10-16 · source ↗ · wrong label?“Recently moved behind cloudflare”
neutral · production · wesleytodd · 2016-08-28 · source ↗ · wrong label?“we switched to using CloudFlare about a month ago after being hit by a DDOS attack (400MB/s incoming traffic).”
neutral · production · williamstein · 2016-05-05 · source ↗ · wrong label?“to send a Slack notification that changes are fully deployed and to flush the Cloudflare cache”
neutral · production · philip1209 · 2015-04-04 · source ↗ · wrong label?“We have CloudFlare set up, but we only plan to turn it on to mitigate DoS attacks”
neutral · production · Sir_Cmpwn · 2013-11-21 · source ↗ · wrong label?