Woke up to a billing alarm email. Thought I had leaked my AWS keys accidentally and somehow run up 437 billion dollars of charges. Joke's on them though, I don't have 437 billion dollars
Anyways I didn't need coffee. That produced an adrenaline release unlike any I've experienced before. Thanks AWS
I'm not a betting person but I am looking forward to the postmortem, whether or not AI was involved, and what their code to production verification stuff looks like now. This kind of thing should have been caught by automated tests.
Woke up to a 100 billion dollars in S3, which is above the USD 4 alarm threshold I had set (I pay $0.55 monthly) . Some AI decided to prune the most impressionable of us.
My 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.
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.
Scared me even though it was obviously a bug once I stopped to consider the magnitude ($bn). Very unfriendly that they don't allow for hard spend caps; closed my mostly dormant personal account as a result.
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.
Jul 17 3:03 AM PDT We continue to work to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. We have identified the root cause as an issue with unit pricing within the estimated billing computation subsystem and we are working on a mitigation. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. Once the issue has been mitigated, we expect full resolution to take multiple hours as we work through recomputing the estimated billing data. We will provide another update by 4:00 AM PDT or sooner if more
information becomes available.
Jul 17 2:07 AM PDT Beginning on July 16 7:38 PM PDT, we began displaying incorrect estimated billing data in the Billing and Cost Management Console. Our engineering teams are engaged and investigating root cause. We will provide another update by 3:00 AM PDT or sooner if more information becomes available.
Jul 17 1:33 AM PDT We are investigating issues with Cost Explorer reflecting inaccurate estimated billing data.
Zimbabwe redenominated its currency three times in 2006, 2008, and 2009, dropping a total of 25 trailing zeros in the process. the 4th Zimbabwean dollar in 2009 was worth 10^25 of the first zimbabwean dollar.
Woke up to a billing alarm email. Thought I had leaked my AWS keys accidentally and somehow run up 437 billion dollars of charges. Joke's on them though, I don't have 437 billion dollars
Anyways I didn't need coffee. That produced an adrenaline release unlike any I've experienced before. Thanks AWS
If you owe AWS 437k bucks, that’s a big problem for you
If you owe AWS 437B bucks, that’s a big problem for AWS
I wonder how many people may have gotten an actual heart infarct because of that. There may be a person out there that may be dead as a result.
It's entirely irresponsible of Amazon to even display such values to the user.
Above a bill of a certain amount, the alert should say "Sit down to view."
huge irl laugh at “i don’t have 437 billion dollars”
Worth a shot to give them a call and explain that. They can probably adjust it down to 100 billion.
What is this, US health care negotiations?
From their status page
>The second path involves rolling back a recent change to the billing computation subsystem.
Want to bet AI code was involved?
I'm not a betting person but I am looking forward to the postmortem, whether or not AI was involved, and what their code to production verification stuff looks like now. This kind of thing should have been caught by automated tests.
>Spawning Sub-Agent: "Dr. Evil"
Is it still a bet if you have 99.999% chance to win?
Can I bet you 437 billion dollars?
Woke up to a 100 billion dollars in S3, which is above the USD 4 alarm threshold I had set (I pay $0.55 monthly) . Some AI decided to prune the most impressionable of us.
You folks are completely irresponsible with your finances. I only spent $2.4 million last night. You've got to learn to manage your money.
Yeah, buy less cappuchinos and avocado toast so you can pay your AWS bills people!
My 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.
Hey man AI makes mistakes sometimes that’s why you need to double check the output.
Yes, there is a known issue with cost estimation.
https://health.aws.amazon.com/health/status
Bit of an understatement: “The displayed billing estimates do not reflect actual usage and charges.”
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.
Thank you. Have seen this after I posted.
Thanks, I panicked logged in and could not find the root cause of the bill.
Thanks AWS, no caffeine needed this morning!
Scared me even though it was obviously a bug once I stopped to consider the magnitude ($bn). Very unfriendly that they don't allow for hard spend caps; closed my mostly dormant personal account as a result.
If they did allow hard spend caps, it sounds like today would be a global outage.
Yeah nearly had a heart attack this morning. Thought keys were leaked for a sec.
Who is going to compensate us for the years taken off our lives when we received the alerts?
My estimate was over 2T. Talk about waking up quickly...
For science I hope people are trying to figure out now how they could manage to rack up a 2T bill in a month.
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.
I have just received a similar alert for $ 5b
AWS on their support data is reporting this:
Inaccurate Estimated Billing Data
Jul 17 3:03 AM PDT We continue to work to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. We have identified the root cause as an issue with unit pricing within the estimated billing computation subsystem and we are working on a mitigation. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. Once the issue has been mitigated, we expect full resolution to take multiple hours as we work through recomputing the estimated billing data. We will provide another update by 4:00 AM PDT or sooner if more information becomes available.
Jul 17 2:07 AM PDT Beginning on July 16 7:38 PM PDT, we began displaying incorrect estimated billing data in the Billing and Cost Management Console. Our engineering teams are engaged and investigating root cause. We will provide another update by 3:00 AM PDT or sooner if more information becomes available.
Jul 17 1:33 AM PDT We are investigating issues with Cost Explorer reflecting inaccurate estimated billing data.
Got a message that I owe 37 million on an account that I haven't used in probably...6 years?
Vibe Billing
"If you owe AWS a hundred thousand dollars, that's your problem. If you owe AWS three billion dollars, that's Amazon's problem."
Heard of somebody who got 19 quadrillion dollars - I thought they meant Zimbabwean dollars
one USD is about 362 Zimbabwean dollars. So it would still be about ~53 trillion dollars which is more than the nominal GDP of US and China combined.
For history here, see https://en.wikipedia.org/wiki/Hyperinflation_in_Zimbabwe
Zimbabwe redenominated its currency three times in 2006, 2008, and 2009, dropping a total of 25 trailing zeros in the process. the 4th Zimbabwean dollar in 2009 was worth 10^25 of the first zimbabwean dollar.
That would have been a great deal!
They should have added "make no mistakes" to the prompt.
Did it recover for you folks? I still see billions of dollars!
far 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.
Prompt: bill our aws customers, make no mistakes.
Prompt: investigate new ways to fund additional AI datacenters.
or: Increase revenue!
I mean just overcharging is one approach to achieving that goal I suppose.
But so is imprisoning or exterminating all humans for their own good, as most AI dystopias end up as.
Mines was $190,594,974,587,761.20 :)
Maybe they accidentally used the Argentine peso ;)
Less hyper-scaler, more hyper-inflation
did it recover for you? I still see billions
131 billion for me