Are you sure it’s a bug ?
The crypto network you hosted should pay for itself in 10-20 years just like LLMs. Don’t worry. Consider Bank of America until then if you are good on credit score.
AWS: Inaccurate Estimated Billing Data – $1.7 billion
121–130 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#122Yes, there is a known issue with cost estimation. https://health.aws.amazon.com/health/status
Whatever you do, AWS, don't post a related service health alert site wide on the console. Heck, don't even post one in the billing module. We wouldn't want to overdo the alerts, especially when we already have one being displayed to market the new FinOps Agent in Public Preview.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#123Probably the closest I've ever been to getting a heart attack. Normally <$1 per month, and now suddenly $284,006,266,443.74. Whatever the bug is on their end, this is unforgivable.
Same here. I got an email with a bill of $233 million and an estimated $433 million until the end of the month. I panicked and nuked my entire setup (which wasn't used that much, anyway, the alert threshold was $1) - I really wonder how many people did the same.
It's been 2 hours and I still haven't fully calmed down.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#124"If you owe AWS a hundred thousand dollars, that's your problem. If you owe AWS three billion dollars, that's Amazon's problem."
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#125Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#126Vibe Billing
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#127far out it's 10pm here and I was just about to sleep when my wife nugged me about a billing alert from AWS.
$151 billion the number for me.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#128Heard of somebody who got 19 quadrillion dollars - I thought they meant Zimbabwean dollars
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#129Mines was $190,594,974,587,761.20 :)
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#130My estimate was only $21M (vs ~$0.01 average bill). Wish I had checked status sooner and saved myself the panic! My process went: verify email is not phishing (it was), login to console and check dashboard (same amount), attempt to understand cost (cost management kept contradicting itself), try to log support ticket and only on that part did I notice the status notification. At least I can breathe again now!
same process, same near heart attack - especially some days ago I had malicious activity on my platform and thought that now they actually found something.
Apparently you can trigger an Action (e.g. prevent uploads) when the billing alert triggers, but then my platform wouldn't work anymore, just because AWS had an issue. Also insane that Amazon still hasn't send an email to clarify.