161–170 of 329 posts
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.
What even is the restriction on returning JSON? One of the examples is explicitly how to return JSON https://developers.cloudflare.com/workers/examples/return-js... From the terms > 2.8 Limitation on Serving Non-HTML Content > The Services are offered primarily as a platform to cache and serve web pages and websites. Unless explicitly included as part of a Paid Service purchased by you, you agree to use the Services…
Seems like my account was restricted due to https://www.cloudflare.com/en-gb/supplemental-terms/#cloudfl ... 2.Cloudflare may, with or without notice to you and without liability of any kind, temporarily limit your storage and/or the number of requests you can make or receive using the Developer Platform for any reason (in its sole reasonable discretion), including without limitation, if processing such requests woul…
It's definitely an unfriendly combo to have (a) a really ambiguous policy like 2.8 and (b) enforcing via a no-warning cutoff -- even if the two policies have good justifications individually. But I wouldn't jump to the conclusion that part (b) is part of the sales strategy. (Part (a) obviously is meant to incentivize a paid account for applications like yours.)
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…
Earlier quoted context omitted.
and I really appreciate it, not trying to blame anyone, I created HN post as desperate attempt to have my service online again, hope you understand.
Dude, I'm not mad at you for reporting it. I'm working internally to figure out why your site was throttled and take appropriate action.
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.
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.
Cloudflare has non-transparent pricing, unlike AWS, which will charge you for every thing with detailed usage tracking. When ever there is non-transparent pricing, it's scary to try and use an infrastructure related service. The sales teams can't go around saying that you are not a profitable customer, and they can't argue with the marketing team to be more honest about pricing on the pricing page. So, end result, le…
I get more worried when the giveaways / marketing is VC funded - they often end at some point or pressure inside to dial back etc.
“We have free egress to Oceania!” - no, you don’t. You are subsidizing that.
Given what aws charges and how they charge for almost everything- no reason to be any pressure to move me to another plan. AWS free tiers are relatively minuscule
Earlier quoted context omitted.
I'm always unsure how to read this. One one hand it is nice that there is someone in the company willing to do work which is in the interest of the customer (of sorts). But on the other hand it shows the company is willing to let quality, support, customer care, service and everything else decline but when it comes to public image is prepared to do everything within their power, even (yuck) their job in order for dam…
It doesn't make the problem go away by itself, but I would rather have jgrahamc helping people than not.
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).
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.
To those continuing to foam at the mouth: what would be the ideal outcome? Cloudflare closing up shop entirely after this? The whole "this shouldn't have happened in the first place" mentality is completely unproductive.