Live data from Hacker News

Small SaaS banned by Cloudflare after 4 years of being paying customer

news.ycombinator.com

151–160 of 329 posts

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#151
post #31

Earlier quoted context omitted.

That response misses the point by a wide margin.

Not a big surprise given they think HN threads are an acceptable form of customer support for paying customers.

It’s an acceptable form of support as long as it’s reliable.

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#152
I stopped paying for cloudflare after their support team was unable to debug why one of my rewrite conditions wasn't working. I provided them full details like for kindergarden, but they replied after days saying it's working on their end, lol. I deeply respect the cloudflare tech and the dev team, but support sucks and i don't trust cloudflare anymore. I won't pay even a single cent, even if they would have stellar support from now on. After reading all these cloudflare stories lately, and knowing how they treated me, i don't care about them anymore. Someone should write a "you probably dont need cloudflare" article. I'm disgusted by these kind of companies that grow large and they stop caring for the people who were there with them from day 1.

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#153
post #28

Cloudflare: MitMaaS https://framagit.org/dCF/deCloudflare/-/blob/master/readme/e...

All of that is well known surely, it's still the site owners choice, including whether to block tor traffic which is often the source of these issues.

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#154

> when I got approached by Cloudflare sales team I explicitly asked if I can still be on pay as you go/self server model and reply was: Never entirely trust what is said to you to secure/continue a sale, unless you have it written in a contract. > … "Enterprise wise, that's up to you and you could likely get away with utilising self-serve as you go … especially if what sales say to you is couched in vague works like…

> Never entirely trust what is said to you to secure/continue a sale, unless you have it written in a contract. This time last week, Cloudflare shut off our access to one of their services we were using because we went over quota. Well, we had actually negotiated overage charges and did actually have this in our contract. They turned the service off anyway instead of applying the overage charges we had agreed. This i…

That sounds more or less the same as everything AWS produces.

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#155

Literally just sent an email to my devops guys to move off cloudflare asap. This cavalier lack of respect is a diservice and insult to all the people who rely on my product for their livelihood.

This is the height of knee-jerk reactions, worse still it's largely pointless. Unless you're big enough to negotiate a specific contract with a cloud provider you're always going to be at the mercy of their catch-all policy.

The only way to actually be protected in this case is to run a multi-cloud strategy. Even then it's only going to protect you so far if you piss off the powers-that-be / community (see the hosting trouble Parler had as an example, not that I'm fond of Parler or anything).

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#156

Around 12:00 UTC today ban has been lifted for my account thanks to @jgrahamc - thanks!

So HN to the rescue again. It's unfortunate (although the outcome is great for you!) that you have to go through the social media amplifier first.

Perhaps there should be a site with metrics on which services only provide social media outrage mediated support.

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#157

Earlier quoted context omitted.

> Since then I also contacted with sales team … in order to upgrade to Enterprise plan as it seems like the only solution Talk about coercion. Considering that you weren’t, technically speaking, violating any terms of service, this response from them leaves a very bitter taste in my mouth. Good luck, and thank you for sharing this with us all.

Around 12:00UTC today ban has been lifted for my account thanks to @jgrahamc - thanks!

So you got a 12 hour outage over... Some random automated system kicking you off their platform for serving non-HTML in requests, which they demonstrate doing in their documentation?

Truly amazing.

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#158

Earlier quoted context omitted.

You’re changing your arch because you saw a one-sided completely unverified post on HN? At this point @jgrahamc has the worst of it - people show up here time after time hoping they can make enough of a stink to get him involved.

When they could just email me (jgc@cloudflare.com)

Had similar issue in recent past, and was able to get it solved via the Discord channel. From what I understood is that it requires a manual over-ride on R2/ Workers because the thing that checks for the 2.8 TOS violation is not able to see the difference between Workers/ R2 and the standard CDN service.

If you go to the R2 Discord channel you see this happening every other week.

What is also kinda annoying is customers can't create support tickets because it requires a plan. Which imo is bad given these customers pay for R2 and often have a ton of data on it (which is why the 2.8 gets hit...).

Hopefully you can get this fixed permanently (for all customers at once, and not case-by-case).

Re: Small SaaS banned by Cloudflare after 4 years of being paying customer

#159
post #137

Earlier quoted context omitted.

So HN to the rescue again. It's unfortunate (although the outcome is great for you!) that you have to go through the social media amplifier first.

Personally I maintain my opinion that problems getting fixed by HN are a bigger red flag than problems not getting fixed at all. The HN reader Upper Management Person either thinks putting out fires before they become higher profile failures is a cheaper way of avoiding bad press than instituting actual good policies with regards to not fucking over their customers, or they want to implement those policies but are no…

It's very common that you need someone's details to fix their situation right away, and avoiding similar situations in the future will take relatively slow engineering and policy changes. Additionally, details about a particular person's case can be helpful in understanding how exactly your process went wrong. Asking for details is not a red flag to me at all.
Post reply on HN