Live data from Hacker News

Netlify just sent me a $104k bill for a simple static site

old.reddit.com

551–560 of 836 posts

Re: Netlify just sent me a $104k bill for a simple static site

#551
post #525

Earlier quoted context omitted.

I agree completely with the underlying principles, I just think once the CEO has commented and stirred up some interesting discussion that's relevant to a large segment of your userbase, the thread doesn't really belong to some generic "customer service shitstorms" category anymore. I learnt more about Netlify, Vercel etc and how they operate from this thread from the last 100 "customer service" threads combined. I l…

Ok, let's try that and see what happens!

"Is that you, Rabbit?" said Pooh.

"Let's pretend it isn't," said Rabbit, "and let's see what happens."

Re: Netlify just sent me a $104k bill for a simple static site

#552

Earlier quoted context omitted.

There are only two questions everyone have: 1. Would Netlify forgive the bill if this didn't go viral? 2. How do you plan to address this issue so that it never happens again? Everyone here knew someone from Netlify would come and say OP wouldn't have to pay. That was a given. Now we want to know the important answers.

1. Yes. We've forgiven lots and lots of bills over the last 9 years and they haven't gone viral 2. While I've always favored erring towards keeping people's sites up we are currently working on changing the default behavior to never let free sites incur overages

Give that there are free stressers/booters , and reasonable prices to rent a DDoS cloud.... https://stresser.su/#pricing

1. What are you doing to prevent DDoS's from hitting your network?

2. Why do customers have to allow an unlimited credit burden to use services?

3. Why arent there cost controls to "if $$ exceeds X, shut acct down"? Azure can do this.

Long story short, why are you by default (except for social media escalation) passing fraud costs to customers?

Re: Netlify just sent me a $104k bill for a simple static site

#554
post #418

Earlier quoted context omitted.

We did this at DigitalOcean for similar reasons, wasn't a feature that was commonly used. Additionally, when you set that limit people then get upset because usually when they go over it for a good reason, like going viral, they aren't anticipating it, and just when their traffic is most valuable the site is down. What Netlify is doing here is really the best approach for both parties. And typically speaking a $104k…

A debt is still a debt even charged back. There would be many attorneys interested in collecting a $105k debt.

No, not really. Not really what attorneys do. There might be collections agencies interested in recovering the debt, but if it's some rando guy who doesn't have the money, even that is open to debate.

I mean I'm not familiar with every debt collection scenario under the sun but Internet randos seem to think this is a real thing where like a cloud/hosting company sends an army of lawyers to repo some guy's house and runs him into bankruptcy because of a traffic overage. I've never seen it work that way, what happens like with most business debts, is someone at the company negotiates with the debtor to try and get as much out of them as they can, and failing that, possibly refers it to a collections agency which does the same but plays a bit more hardball.

In the case here with Netlify even before it went viral they reduced the amount from $104K to $5K, no lawyers, collectors or repo men involved, and while I'd hate to be stuck with that $5K bill, I dunno, that does feel closer to the mark of something that maybe you should be on the hook for if you're responsible for 200 TB of bandwidth overage over 4 days? Is this so bad on the part of Netlify?

All that said I'll just add that I've never given my credit card to any sort of host/cloud who had terms where they could bill unlimited overage fees like this. Never will unless there's a cap. Not Netlify not AWS not nobody. That goes for my personal life as well as for the business I operate. The terms is the terms and the answer is to not use these services unless you can afford them imho.

Re: Netlify just sent me a $104k bill for a simple static site

#555

Earlier quoted context omitted.

1. Yes. We've forgiven lots and lots of bills over the last 9 years and they haven't gone viral 2. While I've always favored erring towards keeping people's sites up we are currently working on changing the default behavior to never let free sites incur overages

Any cloud platform should have a spend-stop amount built in. i.e. if I know I average $10 a day, I should be able to put in a "If it hits $50, email me and take it offline". Of course the opposite problem is then people setting that limit too low but since the user defines the limit that's on them not you. This is one of the reasons I still in 2024 rent physical boxes and run the modern stuff on top of them directly,…

This is something I really like about Nearly Free Speech.net. Their model is that you deposit funds up front, and they will deduct from those funds as you use services. It helps that they actually are nearly free so that a single $20 deposit can last for months or years in many cases.

It's bizarre to me that more services don't support billing this way, since there are tons of situations where I would much rather have a site or service go down than be hit with a surprise bill and have to depend on social media and magnanimous corporate PR.

Re: Netlify just sent me a $104k bill for a simple static site

#557
post #418

Earlier quoted context omitted.

Any cloud platform should have a spend-stop amount built in. i.e. if I know I average $10 a day, I should be able to put in a "If it hits $50, email me and take it offline". Of course the opposite problem is then people setting that limit too low but since the user defines the limit that's on them not you. This is one of the reasons I still in 2024 rent physical boxes and run the modern stuff on top of them directly,…

We did this at DigitalOcean for similar reasons, wasn't a feature that was commonly used. Additionally, when you set that limit people then get upset because usually when they go over it for a good reason, like going viral, they aren't anticipating it, and just when their traffic is most valuable the site is down. What Netlify is doing here is really the best approach for both parties. And typically speaking a $104k…

It seems like that could be an option like:

Hard limit: [$1000]/mth or [$500]/24hr period

Notify me if traffic exceeds thresholds: [$800+]/mth or [$400]/24 hr period

Notify me if the traffic forecast for the month looks like it will exceed my hard limit before the end of the month.

Re: Netlify just sent me a $104k bill for a simple static site

#558
post #452

Earlier quoted context omitted.

> Cloudflare's ddos protection Yeah, we got hammered once with over 10TB/mo and noped out of Netlify as fast as we could: https://twitter.com/rethinkdns/status/1370342245841342466 Had to pay the bill in full. Cloudflare's free tier is ridiculous: We do over 30TB+ of genuine traffic for $0. Makes it hard to move to any other platform. As a small tech shop, this is my Hotel California I'm happy to never leave.

> Cloudflare's free tier is ridiculous: We do over 30TB+ of genuine traffic for $0 It's not really ridiculous if you think about what you're giving them. You are massively benefiting their platform by providing them data which they use to train their services and then sell those services to other customers. I'd make a case that the data they collect is the most important part of their business and the free tier is a…

If you are not paying for it, you are not the customer; you're the product being sold.

Re: Netlify just sent me a $104k bill for a simple static site

#559
post #418

Earlier quoted context omitted.

We did this at DigitalOcean for similar reasons, wasn't a feature that was commonly used. Additionally, when you set that limit people then get upset because usually when they go over it for a good reason, like going viral, they aren't anticipating it, and just when their traffic is most valuable the site is down. What Netlify is doing here is really the best approach for both parties. And typically speaking a $104k…

Here's an idea: let users set a spending limit. If they're about to go over, shoot them a quick heads-up and give them 24 hours to sort things out or level up their package. After that, if they haven't made any changes, temporarily pause their site access

AWS budgets are good for the first part, but they have no interest in a hard cap for obvious reasons.

Re: Netlify just sent me a $104k bill for a simple static site

#560
I guess I never want my personal blog/site to be successful. Can't trust that I will wake up to a huge bill from EC2 or my CDN provider. Feels like health insurance in that even when you have insurance, you are never 100% confident you will not get some huge hospital bill. The pessimistic part of me says this is all deliberate to prevent the "little guy" from competing these days.
Post reply on HN