Top
Best
New

Posted by nprateem 17 hours ago

AWS: Inaccurate Estimated Billing Data – $1.7 billion

URL already posted: https://health.aws.amazon.com/health/status

I've got an estimated bill for $1.7 BILLION over this month. Normal usage is < $5.

Obvs have created an urgent AWS support ticket. Anyone else seeing something like this?

Update: Reddit link: https://www.reddit.com/r/aws/comments/1uyuaw7/help_my_bill_s...

1057 points | 643 commentspage 6
craigmoliver 13 hours ago|
Ditto on the heart attack. My cost estimate for the month is currently $223,509,270,216.17. My girlfriend suggested contacting Elon for help. Glad I found this thread. Maybe I should create new keys anyway, this stuff freaks me out.
_joel 14 hours ago||
I've had a mysterious Neptune cluster appear on my billing. Never used it, no API key access (or IAM instance profile access, OIDC etc), nothing in my console shows I've ever had one in any region. Raised a case with support, they ignored it.
szge 11 hours ago||
I wonder what's going on; they still don't have a potential solution after 7 hours and they have multiple teams on it. Never seen anything quite like this
mlitwiniuk 17 hours ago||
I was actually in the toilet when I got an email I owe them $36,869,876,146.51. I literally just shit myself.
mlitwiniuk 13 hours ago||
Ok, back to $0.17 :D
andystanton 17 hours ago|||
Mine was about the same and evoked a similar response.
Hamuko 17 hours ago||
I got one for 8 billion while I was eating lunch. Thankfully I managed to not vomit.
Sheepzez 16 hours ago||
Yes, I've got an estimated bill of $4bn. Probably related to the ongoing "Inaccurate Estimated Billing Data" incident?

https://health.aws.amazon.com/health/status

port3000 15 hours ago||
They have to pay for that AI Capex buildout somehow
scrapcode 12 hours ago||
Tale as old as time. When I was coming up it took a $20-40/m investment to get a "dedicated" server that you could start tinkering around on. When you couldn't afford that, you bricked the family PC trying to figure out how to configure your own LAMP stack.

Nowadays you just have to risk accidentally billing your parents CC the tune of multi-generation wealth to get that real-world experience.

danny_codes 12 hours ago||
Hetzner has hard usage cutoffs
Imustaskforhelp 6 hours ago||
No not really, nobody has to be using AWS itself per se to be honest, there are still alternatives around.

I mean I own a 7$/yr vps that I pay with crypto and my stack usually involves golang/rust and oh I also self host my mail for temp-mail esque things on that server and I have some other servers floating around as well.

Its just that everyone uses AWS which is the wrong issue here to be honest. If you ask me, aside from the ram pricing caused by AI inflation, things are pretty good. The issue is that not many people know about server providers and other things and default to AWS/Azure etc. because big companies and small companies alike are using them.

Here's a global (interactive) visualization of around ~250 providers, 224 locations and 800 distinct links in 60 countries that I have made if this space interests ya: https://buyvds.net

daft_pink 11 hours ago||
Maybe it’s one of those absurd situations where canceling a service doesn’t actually stop the charges. Instead, they quietly begin billing you for some random add-on that was bundled with the original service. You never knew it existed, never knew it had to be canceled separately, and now you’re paying full price for a completely pointless ghost service because the only thing it was tied to has already been canceled.

It sounds ridiculous, but something very similar happened to me with Amazon WorkSpaces. During the WorkSpaces setup, an AWS Active Directory (Directory Service) instance was provisioned as part of the deployment. When I later canceled WorkSpaces, I had no idea the Directory Service had to be deleted separately. I kept getting billed for it, and it ultimately cost more per month than the WorkSpace itself had.

sankalpmukim 15 hours ago||
AWS pushed the wishful thinking internal calculator to production.
sierra1011 6 hours ago|
I got an email this morning.

> You requested that we alert you when the actual cost associated with your Monthly AWS budget exceeds $2.00 for the current month. The month actual cost associated with this budget is $646,677,805.51.

Current usage: $1.70.

I called it a rounding error and figured it would wash out within a couple of days...

More comments...