How do we know if our bills were ever right if this made it into production?
That's the neat part, you don't!
AWS: Inaccurate Estimated Billing Data – $1.7 billion
251–260 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#252a billion here, a billion there, sooner or later it adds up
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#253Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#254AWS saw Anthropic billing a guy for $16 million on zero usage and thought, why stop at the millions?
https://www.techtimes.com/articles/320266/20260712/anthropic...
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#255Earlier quoted context omitted.
I mean, emotional damages are a thing right?
Not really in the way the media would have you believe. Like “I was scared for a couple minutes on a Friday morning until I saw the vendor status page” is orders of magnitude away from the bar here.
I wonder how many people died of heart attack when they saw this.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#256As 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.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#257I feel much better after seeing the $B estimates here; I only have an estimate of $34M so far Folks can track it directly on AWS Health: https://health.aws.amazon.com/health/status
It's ok, I owe them 1.22 trillion.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#258To be exactly that guy:
This cannot happen if you do not do this renting at variable rates.
A thing you own doesn't suddenly bill you trillions of dollars in error. It doesn't hyperscale either, but neither do you.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#259Apparently what used to be `GB of storage consumed` is confused with `Bytes of storage consumed`, leading to a cool off by 2*30 error. > You're right to question my calculation. The MCP server failed to connect when I tried to look up the field definition. I guessed instead of validating. This is on me. But look at all the revenue!
Vibecoded the billing system, raised revenue 9000%. Great for that promo package.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#260Apparently what used to be `GB of storage consumed` is confused with `Bytes of storage consumed`, leading to a cool off by 2*30 error. > You're right to question my calculation. The MCP server failed to connect when I tried to look up the field definition. I guessed instead of validating. This is on me. But look at all the revenue!
Oh great so 2*30=60 he only owes 28.3$ million... hehe
I guess you wanted to say 2^30 which makes 1.5$