Does the affiliate program still work for AWS? When do I get my referral fee?
AWS: Inaccurate Estimated Billing Data – $1.7 billion
331–340 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#332As someone who usually works with data analysis, the distribution of the numbers strikes me as odd. Almost all of them have one number that appears four times, and one or two that appear three times. And overall, there are an unusually small number (0–9) of digits that appear at all. Maybe it's not just vibe-coded, maybe the numbers themselves are being hallucinated by an LLM.
Someone said the numbers are all off by 2^30 because they screwed up and are charging the per GB price for each byte. It’s probably an artifact of them all being currency multiples of 2^30
Well, for my case, I was paying $0 (Exactly, I managed to hunt down and delete every last resource in my account a few months ago). It was displaying $430 million for me. I don't think that is 0*2^30.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#333invoicemaxxing
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#334Earlier quoted context omitted.
For science I hope people are trying to figure out now how they could manage to rack up a 2T bill in a month.
My immediate thought was that someone managed to get an access key, stuffed a ton of data in there, and then was doing a ridiculous amount of egress. That was the only way I could conceivably coming up with anywhere near that much cost.
I doubt AWS has capability to do anything to generate $2T of charges, even if one user maxed every billable capability of every resource they have.
If I got an email with that amount I would've just laughed at the incompetence that lead to a bug that lead to me getting the email. But I write as a backseat email recipient.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#335Earlier quoted context omitted.
That job description feels so far beyond parody that I could scarcely believe it until opening the link! What a world.
It gets worst: "Senior Software Development Manager, AWS Global Bill Generation" https://www.amazon.jobs/de/jobs/10471948/senior-software-dev... "We're transforming from monthly batch processing and manual war rooms to continuous billing, autonomous agents, and self-healing infrastructure. We believe operational burden is a technical problem, not a staffing problem" This looks clearly...a staffing problem...
> This looks clearly...a staffing problem..
I think that big tech recently decided that I got 99 problems but staffing ain't one
I guess Nothing is a staffing problem when you make a rule that firing people is always the solution.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#336One user posted a screenshot: https://prnt.sc/UqjcYD3RSQrS Edit: I was just about to credit the user when my internet dropped. The source was here: https://news.ycombinator.com/item?id=48945606 - thanks mirzap!
Wow, $139 B.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#337Our org account's bill is showing up as > 100 trillion.
You've got to grab a screenshot of that.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#338Me too, hello all. I've got 59 Million dollars in billing threshold reached email from AWS. And felt the same as others, and after half an hour of investigation I saw their message on top of the support page. I have 6 mb for static website stores in S3. No other resources.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#339I realized recently that Whole Foods no longer automatically and reliably detects your Chase Amazon Prime credit card when paying. So they don’t give you the discounted pricing automatically. I wonder how many customers are checking out the way they always do and are paying full price when, for years and decades, this worked fine. The customer service people I talked to in the grocery store said this changed sometime…
Class action lawsuit time! Either that or 1000’s of small claims court cases. Even with arbitration, the overhead of dealing with that would be crippling. Hopefully someone over there decides to do the right thing, and auto-refund.
Relevant to this, I've recently noticed a trend of mass tort cases being opened up in the past couple years, and they seem to do very well. The way these seem to work is attorneys identify a company who has clearly ripped people off, and what I presume is a repeatable way to guarantee a win (thus translating to a guaranteed settlement offer). Then they advertise for eligible clients, sign those clients individually to contingency agreements, and run the playbook. A couple months ago after signing up for one of these, I received a check for about $350 (after the agreed-upon 40% attorney fee), from Ticketmaster, and I had another one related to AT&T. It took about 10 minutes more effort from me than a typical class-action settlement, because I had to e-sign those representation papers.
So really, there's a third option now, that's much easier than class action, even when class actions don't get certified.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#340I realized recently that Whole Foods no longer automatically and reliably detects your Chase Amazon Prime credit card when paying. So they don’t give you the discounted pricing automatically. I wonder how many customers are checking out the way they always do and are paying full price when, for years and decades, this worked fine. The customer service people I talked to in the grocery store said this changed sometime…
There are a hundred small things like this that seem to be popping up in what used to be simple and reliable systems and as much as I know they aren’t ALL because of vibe coding I can’t help but wonder how much is.