Live data from Hacker News

Paid $2400 to Cloudflare, support refuses to help

news.ycombinator.com

1–10 of 31 posts

Paid $2400 to Cloudflare, support refuses to help

#1
I signed up for Cloudflare's Business plan and paid for a year in advance. While adding a new domain I made a typo and now the subscription is stuck in a limbo.

I can't change the domain without contacting their support or paying another $2400. When I open a support ticket, their portal shows 'Unable to find your account' and tells me to open another support request for it.

All support tickets are closed automatically by their "AI" which points to the same article that says open a ticket.

Is shaming them on Twitter my only option left?

Re: Paid $2400 to Cloudflare, support refuses to help

#4
One of the things I was most surprised about recently is just how buggy and unpleasant to use the Cloudflare dashboard is. We only moved to them recently and I was really shocked. I had one situation where the dashboard literally showed me the wrong domain but rules for another, which I think was a session or caching bug. I really thought it would be better for a company that size!

Re: Paid $2400 to Cloudflare, support refuses to help

#8
This would be an excellent use of small claims court; you want paid-for service provided and they’re giving you the phone-tree runaround. The court would prefer a settlement be reached before trial and their legal team will have no trouble bypassing their support AI to get a ticket opened.

Re: Paid $2400 to Cloudflare, support refuses to help

#9
post #4

One of the things I was most surprised about recently is just how buggy and unpleasant to use the Cloudflare dashboard is. We only moved to them recently and I was really shocked. I had one situation where the dashboard literally showed me the wrong domain but rules for another, which I think was a session or caching bug. I really thought it would be better for a company that size!

You'd be surprised... I did a LOT of cleanup work for a private college that had a lot of "clever" developers that didn't understand static variables in C#, or how the ASP.Net lifecycle worked. Race conditions and all kinds of weird errors when the system got busy. Not to mention a lot of "fun" performance issues.

Just because someone has a CS degree doesn't mean they actually know what they're doing.

Post reply on HN