Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 329 posts

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

#121

Post by ignoramous »

ddorian43 wrote: post #22
tardis_thad wrote: post #20

Earlier quoted context omitted.

I'm using Workers as basically API gateway/smart load balancer to backend services that handle actual load (resource intensive data filtering). Most of the responses are not cached on Cloudflare level. Thing is that I was using Workers for about 4 years already with not issue at at all, I'm aware that I use lots of requests and bandwidth but I just wish I was contacted about mandatory upgrade before effectively turni…

How much are you paying for the workers/month? Why didn't you use the load-balancer service?

> Why didn't you use the load-balancer service?

Speaking from experience, if you only need rudimentary L7 load balancing, then Cloudflare Workers is as good as it gets.

> How much are you paying for the workers/month?

Per my estimate, probably between $600 to $2000 for Workers: https://news.ycombinator.com/item?id=34639930

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

#122

Post by rightbyte »

twawaaay wrote: post #88
Dowwie wrote: post #81

4 Billion requests per month involving 1 Petabyte of traffic doesn't seem like a "small SAAS", at least packet-wise. If its small revenue-wise, addressing that is a business concern as important as having your platform throttled for using the cheapo economy edition tier of whatever you've signed up for with Cloudflare. Did Cloudflare issue any formal communication with you warning about usage and how it violates cont…

I worked for a large bank, my internal backend would receive couple orders more requests from other internal apps and users and probably similar traffic. It is very easy (relatively) to build a SaaS platform that serves this amount of traffic and this can be done by even a one determined individual or a small startup team. I don't think it is useful to measure the size of the company in the amount of requests they ar…

Are you doing RAM-aaS or something?

Must be alot of redundant data back and forth.

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

#123

Post by undefinedzero »

jgrahamc wrote: post #82
Veen wrote: post #74

Earlier quoted context omitted.

Friendly advice, stop digging and step away from this thread/talk to your PR team. You're not helping yourself or Cloudflare by responding in this way.

You're right. I'm taking all this too personally.

Wow this is the worst take about customer service I have ever seen by a company. You cause huge issues for business with the touch of a button, and when they require help and don’t think the cause was acceptable behavior, they’re whining? Just wow.

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

#124

Post by tardis_thad »

lolcrow wrote: post #55

Maybe they booted you because your business model is to use Cloudflare to repeatedly and aggressively scrape data from cryptocurrency exchanges and then resell it for hundreds of dollars a month. Sounds like an abuse of their terms of service to me.

Cloudflare is not used at all for data collection (it's not scraping, it's using official exchanges APIs), only for the APIs that serve historical data.

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

#126

Post by jgrahamc »

undefinedzero wrote: post #123
jgrahamc wrote: post #82

Earlier quoted context omitted.

You're right. I'm taking all this too personally.

Wow this is the worst take about customer service I have ever seen by a company. You cause huge issues for business with the touch of a button, and when they require help and don’t think the cause was acceptable behavior, they’re whining? Just wow.

I've removed the word "whining" but to be clear I was not talking about the person who posted on HN that they had a problem. I immediately jumped on their problem when I saw it and I've ended up spending almost all morning on it. I took the long threads personally and should not have done.

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

#127

Post by batter »

rafaelturk wrote: post #93

I really curious about how this unfolds, I was planning to migrate from AWS Lambda to Cloudflare Workers. And we have LOTs of Json, and APIs. Why would they cancel paying Workers customers?

If you're looking eagerly to replace human support with searches of someone from CF on HN to help... why not.

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

#128

Post by BasedInfra »

cultofmetatron wrote: post #116
kkielhofner wrote: post #111

Earlier quoted context omitted.

If you’re using Cloudflare for DNS/registrar they have pass-through pricing. It’s a loss for them - you’re not paying for anything.

Thats even more reason to switch to Route 53. I didn't choose cloudflare at the beginning but its clear its a bit of a liability here. To put it in perspective, we had to send out apology emails to very irate customers when our system went down for 10 minutes in December. edit: Route 53 not S3*

You use Cloudflare for DNS but are moving over to S3 to replace Cloudflare?

Do you not mean Route 53, AWS’s DNS product?

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

#129

Post by nubinetwork »

fragmede wrote: post #70
nubinetwork wrote: post #44

Earlier quoted context omitted.

Actually, my mistake... it was almost 3 weeks ago. https://news.ycombinator.com/item?id=34383720 https://web.archive.org/web/20230114202232/https://news.ycom...

Ah damn, all it says is "I was advised to remove this post" and what was there before is not in archive.is

The OP got saved in the wayback, I edited my earlier post with the link.

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

#130

Post by shireboy »

cultofmetatron wrote: post #104
kkielhofner wrote: post #78

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.

we use cloudflare for their dns so not a complete change of arch. (this kind of lockin is precisely why I've stayed away from faas) more importantly, its important to send a message. We depend on these services for our livelihood. if I'm paying for a service, the least I'm owed is the ability to get in touch with a person to rectify the situation as soon as possible. Companies who want other companies relaying on the…

Totally agree they should have provided a warning. Any Saas (and really would apply to social media, web mail, etc) should clearly warn before taking drastic action if possible. But I don’t see how you’d have dns without vendor lockin. It’s not like moving dns to godaddy would be better. Route53 is nice, but aws is also a vendor lots of people are locked to

Similar for ddos protection- you almost have to use somebody.

Post reply on HN