zlacker

>>tardis+(OP)
OP, you have garnered a lot of sympathy by the HN community which I believe in part contributed to your problem being resolved. I think it would be fair to provide more info about what the issue was in the end. It's not OK to be like "HN I had a bad experience with Company X" and then be like "k, thx @jgrahamc, bye" when your complaint gets resolved due to the attention it received.

There are so many questions this leaves unanswered:

- Was this a one-off error in Cloudflare's processes? (These things happen on a big enough scale.)

- Were you violating a specific clause of Cloudflare's T&C? How clear was the clause? What did you do to fix this?

- Was the issue that Cloudflare estimated that you're not paying enough given the bandwidth you're consuming? Did you end up signing up for the Enterprise plan?

Transparency would benefit both Cloudflare (in not making people unnecessarily apprehensive about becoming/remaining a customer) and you (in demonstrating that you're handling this issue in a professional and responsible manner).

>>plesiv+Sw
oh it is 100% entirely OK to share that you got screwed by a company .. this crap happens all the time.. companies like this get away with ZERO shits give about customer support all the time.. it is insane..

>>dezb+tA
Not that this is true in this case, but a large number of HN support thread creators are very cagey about the nature of their business. I suspect a lot of the time they know they broke the ToS and are hoping that HN will get the pitchforks out to help them get their way regardless.

Again, that doesn't seem to apply here, but I've stopped assuming that the existence of an HN support thread by itself shows malfeasance or incompetence on the part of the company.