Anyways I didn't need coffee. That produced an adrenaline release unlike any I've experienced before. Thanks AWS
It's entirely irresponsible of Amazon to even display such values to the user.
https://edition.cnn.com/2021/07/01/business/robinhood-lawsui...
>The second path involves rolling back a recent change to the billing computation subsystem.
Want to bet AI code was involved?
https://www.theregister.com/software/2026/02/24/aws-would-ra...
AI: "No problem, let me change how we bill and fix the tests for the new increase in value"
Of course, you provided heart stress failure tests for free.
Thanks AWS, no caffeine needed this morning!
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!
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.
I was on the phone with him and we checked that he didn’t leak any APIs keys but no traffic at all. I even thought of a breach at a vendor he uses for some s3 stuff before I found this thread on HN.
You can use the search box at the bottom of every page to search for previous posts.
This was posted an hour before you posted: https://news.ycombinator.com/item?id=48945241
Love to see how hyperscalers make your life easier and less worrying.
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.
Long story short: it saved the company from irrelevance. “Well-architected” is for the hyperscalers’ balance sheet, not yours.
https://news.ycombinator.com/item?id=48945233
OT: $286 million for me, almost had a heart attack
Even though I new they could not collect the whole amount, I wondered whether I was hacked. I closed the account, it was an old testing account anyways.
$151 billion the number for me.
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.
My personal website is on Lightsail, but those alerts started popping up from some test services I had set up while I was studying AI. I swear my heart nearly stopped and I cried. I really think AWS should have spending limits in place.
My bank account barely has enough for next month's rent.
You don't need hours to recalculate billing. You need to go back to basic algebra.
Anyone using Amazon and dealing with this should be moving away from their services because something this basic going wrong means the correct people are not at the helm of the ship.