AWS: Inaccurate Estimated Billing Data – $1.7 billion
415 points by nprateem 6 hours ago
415 points by nprateem 6 hours ago
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...
I got 3 consecutive emails warning that my budget crossed its $18 threshold. Opened it up: cost was 78 million. Thought it was a phishing attempt, logged into my actual account, and... still 78 million. EMOTIONAL DAMAGE. Wanna bet the description of this job post will be updated by the end of the day? "Software Development Engineer II, AWS Invoicing" https://www.amazon.jobs/de/jobs/10428480/software-developmen... "...Our platforms are powered by generative AI, large language models, knowledge graphs, and agentic architectures that dynamically compose specialized agents based on context. We apply these capabilities across three reinforcing areas: intelligent launch readiness — where autonomous AI agents analyze, generate, and validate the information needed to go
live in a new market; cloud-native service orchestration — where configuration-driven microservices replace per-launch bespoke engineering with centralized, reusable capabilities so that expanding into a new country becomes a zero-code configuration change rather than a development cycle; and continuous validation..." Wow: I just find it funny how people claim that LLMs will put money in the hands of domain experts. There’s not a single damn bullet about the fucking domain lol. The irony is, the only purely deterministic thing, will be token consumption... I severely doubt the world ever gets to such a point that the entire world melts into AI hallucination. And token consumption depends on so many other things, it's not all that deterministic either. (token usage) is trending towards predictability for a lot of reasons. it's not deterministic but it's getting easier to reason about usage. That job description feels so far beyond parody that I could scarcely believe it until opening the link! What a world. It gets worst: "Senior Software Development Manager, AWS Global Bill Generation"
https://www.amazon.jobs/de/jobs/10471948/senior-software-dev... "We're transforming from monthly batch processing and manual war rooms to continuous billing, autonomous agents, and self-healing infrastructure. We believe operational burden is a technical problem, not a staffing problem" This looks clearly...a staffing problem... If you can make the software cover the toil you save the staff for the tough cases. > This looks clearly...a staffing problem.. I think that big tech recently decided that I got 99 problems but staffing ain't one I guess Nothing is a staffing problem when you make a rule that firing people is always the solution. I did too, those awstrack.me URL's look super suspicious and I hadn't seen this alert trigger before so didn't know what to expect. At first I was sure it was a phishing attempt. Then went to the console (not using those links)
Saw there was an outage where the console was wrong (no mention of email alerts)
Then I thought I was hacked - what a perfect cover up for someone to evade detection when the console was wrong.
Looked at some logs, realized the incident text was just not exhaustive on the impact.
Went back to my cup of coffee. Note to self- should have looked here first. It's crazy enough this will be fixed soon. Years ago I found an actual hidden error in my bill. (This was early 2010s). The system was calculating the EC2 reservation savings incorrectly for some of my servers. I was crunching all their detailed usage data on a regular basis in an 18 tab spreadsheet and couldn't get it to fully reconcile. I spent months trying to track down the discrepancy. Once I found it, I had to convince AWS their system was wrong, which took another big chunk of time. Meanwhile the discrepancy continued to accumulate. After 14 months I got a $7,000 refund. I was told it had to be approved by the head of AWS. I've never seen a calculation error on their part since. One can almost smell the vibes. This is peanuts compared to a major cybersecurity catastrophe that’s surely in the making. To give credit to the technology and the people using it - and I’m not being facetious - it’s actually incredible that at the current levels of usage the unprecedented catastrophic event has not yet happened. some things never change. Pre AI I was always shocked that such large and complex systems actually run as well as they do. Especially after getting to see how the sausage is made/works. It was the mid 2010s when I sensed a lot of SaaS becoming popular. Just host your ticketing systems, your IT management planes, your security management consoles, your SOC, all off-premises. I wonder if businesses are thinking of ever swinging back to locally hosted, with the increased hostility of the Internet re: AI, vulnerabilities, DoS, and so on. Always messing up some mundane detail! Oh, that's the really fun part. The unprecedented catastrophic event is already happening. Several of them, in fact. By the time we notice, it'll be too late. Clearing LLMs out of our business infrastructure is going to be a massive undertaking. Though I have a tech background, I work in commercial real estate. We are recently seeing new levels of idiocy from the employees, including real estate brokers with zero tech knowledge "coding" solutions to find sites for clients and blindly trusting the output (which I came to find out was complete bullshit), as well as some who have literally stopped communicating with any of their own language - meaning every interaction they have with anyone not in person is made by an LLM. It's a massive threat to our brand and has got to stop. I can't imagine what companies with thousands or tens of thousands of employees who have really been riding the LLM train are going to have to deal with. This thing is more of a virus that exploits human laziness than actual useful tech. Apparently 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! The user is asking me to calculate how much money they should charge their customer. The values they've given me are 0.45, 1.67, and 2.50. This is 2.50 + 1.67 + 0.45 = 4.62, but it could be any other number. Perhaps we should be concatenating the numbers instead. Wait! The . could also mean multiplication. 0 . 45 . 1. 67 . 2 . 50 = 3015000. But wouldn't multiplying by 0 zero it out? That can't be right, we wouldn't be charging anything. So 3015000 must be correct. You should charge your customer 3015000 thousand dollars. > You're right to question my calculation. Literally impossible to tell whether this is parody or an actual response any longer. I challenge anyone to write something so stupid that an LLM couldn't possibly respond with it. I don't believe such limit exists. 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$ My hunch is the HN formatter swallowed the double asterisk typical of python exponents. While we're being pedantic, 2^30 is 28 in normal programming languages ;) Vibecoded the billing system, raised revenue 9000%. Great for that promo package. AI slop. Or just a distracted dev >> Or just a distracted dev And a distracted tester? And a distracted pipeline of regression tests? No, the truth is way worst... Either way it shows their QA and testing procedures are incompetent. It's just not acceptable for a utility like AWS to move fast and break shit. Should make you question whether it's safe or advisable to use any of their services. It probably shouldn't be legal for banks, hospitals, governments, or any other critical infrastructure to be hosted on AWS if they do things like this. 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. AWS 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... If you owe the bank $100, that's your problem. If you owe the bank $1.7 billion, that's the bank's problem. I saw this in action on a smaller scale. In a past job, my wife organized events for a decent sized company. After an event, she'd typically have a $300k+ balance on her corporate Amex. When she went on maternity leave, the person filling in for her job neglected to actually pay the bills, so when she returned there were quite a few emails and voicemails from Amex regarding the over $500k balance. The messages started as polite and eventually started to get more desperate in tone. At no point were they threatening or adversarial. I think that this might reflect more on Amex to be honest. Amex realises that threatening would hurt their business trust more than anything. During the great depression, Amex accepted checks from other banks which were falling and paying through their own wallet as a matter of integrity. Amex has always been built around this idea of trust and prestige. They make most of money from what I have heard on the transaction fees which are more than others (3% compared to 1%). They might get desperate but I am sure that they are one of the last guys who would wanna threaten you if you are paying some large bills for them (as compared to normal credit card companies which might even hire people to extract your loans in some messy situations) So perhaps be so rich that the credit card company understands it as well and treats ya differently :-D Interesting. And hard to square with my perception of banks as completely mercenary and ruthless. I had a decade-long personal boycott (I know, LOL) of Amex after they, because, with otherwise perfect credit, I forgot about a $30 department-store card bill and got a 30-day-late mark on my report, Amex got spooked and abruptly closed both my never-late accounts with them (which were at or close to 0 balances). This was around 2008 though, so perhaps this was a genius algorithm designed to try and detect the very first whiff of consumer defaults, so they assumed that $30 was the first domino to fall of my personal financial ruin that could lead to me charging my accounts to the max and then going bankrupt. (I eventually admitted to myself that Amex isn't a person and thus not really capable of insulting my honor, but it took a while!) This joke only works if you actually impose a cost on AWS of 1.7 billion. If they just serve you a bill for no reason, it's still your problem. Not if you’re Elon Musk I realized recently that Whole Foods no longer automatically and reliably detects your Chase Amazon Prime credit card when paying. So they don’t give you the discounted pricing automatically. I wonder how many customers are checking out the way they always do and are paying full price when, for years and decades, this worked fine. The customer service people I talked to in the grocery store said this changed sometime in the last year. My guess is that it’s an unintended side effect of removing the pay-by-palm feature. This is obviously unrelated but I joked about what else Amazon wasn’t reliably calculating…. Class action lawsuit time! Either that or 1000’s of small claims court cases. Even with arbitration, the overhead of dealing with that would be crippling. Hopefully someone over there decides to do the right thing, and auto-refund. Relevant to this, I've recently noticed a trend of mass tort cases being opened up in the past couple years, and they seem to do very well. The way these seem to work is attorneys identify a company who has clearly ripped people off, and what I presume is a repeatable way to guarantee a win (thus translating to a guaranteed settlement offer). Then they advertise for eligible clients, sign those clients individually to contingency agreements, and run the playbook. A couple months ago after signing up for one of these, I received a check for about $350 (after the agreed-upon 40% attorney fee), from Ticketmaster, and I had another one related to AT&T. It took about 10 minutes more effort from me than a typical class-action settlement, because I had to e-sign those representation papers. So really, there's a third option now, that's much easier than class action, even when class actions don't get certified. There are a hundred small things like this that seem to be popping up in what used to be simple and reliable systems and as much as I know they aren’t ALL because of vibe coding I can’t help but wonder how much is. Weirder is what happened a day later. I got an email that said my Chase Amazon Prime credit card was being re-associated with my Amazon.com account. I never reported this nor took it up with either Amazon or Chase directly. There was a refund of my Whole Foods purchase (they needed to void my purchase and re-ring everything to give me the discounts.. I asked them to refund my purchase and I’d do without my Whole Foods purchase entirely). Looking back I think at least 3 recent visits were charged to me at full price because of all this. Hard not to think of enshittification and whether Amazon Prime is even worth it, alas.. I live in a fairly rural
area at the moment and need delivery. This is just the cloud area, what if Amazon starts vibe charging regular customers because of some bug? Accounts that are directly linked with regular people's payment methods? 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 This just hit global news: https://www.theguardian.com/technology/2026/jul/17/amazon-we... > Amazon Web Services customers receive bills for up to $1.5tn after global glitch Ask for some leniency. Let your account rep know about your budget difficulties and ask if you can make good faith payments of a few billion per month until you get back on your feet. I got a 20K bill once and it was actually drafted from my bank account. It took me a couple of months and involving the office of the AG of my state to get the issue resolved and get my money back. Since then I never touched any AWS product, moved my small stuff to Azure. It’s been years since AWS have these issues with billing, you can find the stories online, students billed 60K for a compromised account launching servers to mine crypto which AWS somehow was unable to flag and block, and let run for months. AWS is basically a utility. I think it's inevitable that their carelessness around billing will end up with them being regulated like one. I wouldn't expect their detection of hacked accounts to be 100% correct. Sure, it might be obvious when a human takes a look, but humans can't proactively look at every account's usage. For a while I had a portion of my "homelab" on AWS. I was an educator in a classroom where the students were learning cloud stuff, and the instructor was encouraging the students to stand-up cloud environments for learning, so I figured that I would do the same. I used AWS' free tier, of course, and I enjoyed the initial setup in EC2, and I did a LAMP-stack MediaWiki installation. It wasn't too difficult, but two things sent me away forever. 1. It was impossible, or at least highly labor-intensive, in this modern era to adequately secure an ordinary Linux system running Internet-facing services. I put fail2ban and I filtered a lot of ports, and still spammers attacked me on Layer 7. 2. It was impossible, actually impossible, to limit or cap my cloud expenses in any billing cycle. Sure, run free-tier all I want. Sure, come in within the limits almost every month. But if I configured one thing wrong, or one thing went runaway, I'd have a sizable bill that I couldn't dispute. And even worse, those "runaways" weren't necessarily things in my sphere of control, but could be triggered by basically anyone coming in and using my VPC resources, especially egress network traffic. So I closed out my cloud account, and I developed a lot of sympathy for businesses and corps that now are forced to run "in the cloud" rather than on-prem or their own machine rooms, but now they have no way to control expenses. That’s why you always use a spend limited card with variable cost providers. Or just own your own hardware. Spend a few bucks at Microcenter, build a machine, and there's simply no mechanism by which they could decide later that you should actually pay 100x more, and then magically suck it out of your bank account. None of this can happen unless you first cede control. I once got a credit card statement that said estimated time to repay ....... more than 100,000 years. It was discouraging but I did pay it off. And sooner than estimated. Were you still alive after paying it off? No, but they have the internet in the afterlife, apparently. That's good for the credit card company, they can project stable revenue 100k years into the future. A guy on the sysadmin subreddit managed to 8x the global GDP https://old.reddit.com/r/sysadmin/comments/1uz2fv2/aws_says_... Vibe coding billing systems is a top-notch idea :) Hey what do you think about vibe coding weapon systems? Do you want to be my cofounder? They sent 3 warnings to my email, ok, I understand bugs happen (probably vibe-coded). But they didn't even send any notification that it's a bug. Going to leave AWS after that. Somehow I highly doubt anyone will leave AWS over this unless their use of AWS is way more low-complexity than the average account. People make similar pronouncements after every us-east-1 outage makes the news, but I feel like AWS would be going out of business by now if people followed through. It reminds me of airlines, where after a particularly grueling irregular ops experience, a few dozen people file off the plane swearing "Never again, <airline name>!" but really, we all must know deep down that the airlines are all subject to the same external inciting factors, internal profit motivations, and human imperfection, and thus all pretty equally likely to cause us a bad day or ruined trip. The effort spent to avoid one isn't really worth it. Probably 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. Yeah, this one is bad because it’s off by so much I’m shocked it wasn’t caught by tests, alerts about unusual changes in the billing system, or even accounting. Like surely the P&L reports look all kinds of wrong right now, they have to be showing like 6M% profit margins and revenue measured in quadrillions. I’m also a little surprised this didn’t trip a circuit breaker. For something as non-real-time as billing, I’m surprised they don’t have an automated kill switch that pauses the billing system and fires a page if variance in bills spikes. Naively some kind of “if the standard deviation of customer bills for this year changes by more than 50%, pause the billing system”. At that number of customers, those numbers should be pretty stable beyond internal billing changes they could normalize for. If I were to guess this bug is in the "display" part of the system which is probably distinct from the "actually take money from the customer" part of the system. One can imagine they have gates on the "actually take money" part, especially for a large bill like ours which was ~$300b or about 2.5x AWS' 2025 revenue... In one month. Surely if we had actually accumulated that bill they would be the ones with the problems when we can't pay it. 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. Same - just had some malicious bots running through my platform last week and really thought they found a security hole after all. Even though the amount sounded ridicoulus, I got quite nervous and a very bad feeling when I logged-in AWS and saw that price. The should pass a law saying they should have to pay you the amount over the correct bill as compensation; I bet they'll stop making mistakes like this pretty quickly after that Same. Cold sweat for about 20 minutes. Even though I saw the service health notification, I still spent the last hour trying to find where my storage spiked. In any case, I'll be tearing down plenty of stale infra after this! Current month
$13,648,114,178,401.01
188,253,226,212% Forecasted month end
$18,729,381,032,152.4 Apparently my company owes the combined GDP of France, Germany, and UK to AWs. "Have you considered using Reserved Instances? You could save up to 2 trillion dollars next month. Book a call with your AWS rep." Probably the safest bet is to pay your bill in full to stay in good standing and then get refunded the difference when they revise it down. Maybe they're using too many humans and not enough AI in their software development. That must be it. The code base is not gigantic enough they need AI to generate massively more lines of code. Well AWS never had bugs before. They need the customers to pay more so they can fix the bugs. It's self-correcting. Wow, those price increases due to the RAM and storage shortages AI caused are brutal. Most likely they also forgot to include "make no mistakes" instructions to their in-house LLM that deploys to production. As 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. > Almost all of them have one number that appears four times, and one or two that appear three times To me that looked suspiciously like string-handling in a weakly typed language. Like when you do `"100" + 1` in JavaScript, or `int("100" * 2)` in Python. I've seen my share of such bugs in PHP, Python, Ruby, JavaScript. In production.
Obviously not as simple as the examples, but subtle, like when a library update changed `someFancyLocalStorage.getOrDefault("lastOrder", 100)` by always casting the value to the type of the default (released as patch release). Or where typedEnvGet() should typecast "numbers", but keeps it a string when theres whitespace `AMOUNT_PER_CALL=100\n`. Or where a number passes through a deep stack of middleware and 99.9% of the times remains an int but in rare race conditions becomes a string. etc. No evidence that's the case here. But from my experience, the repeating and strange formats of numbers hint strongly in that direction. Pedantic as hell but `"100" * 2` in Python (= `"100100"` for those who don't know) isn't really typing, it's operator overloading. Any language with that could implement the same questionable design decision. Someone said the numbers are all off by 2^30 because they screwed up and are charging the per GB price for each byte. It’s probably an artifact of them all being currency multiples of 2^30 Well, for my case, I was paying $0 (Exactly, I managed to hunt down and delete every last resource in my account a few months ago). It was displaying $430 million for me. I don't think that is 0*2^30. https://health.aws.amazon.com/health/status "Operational issue - AWS Billing Console (Global)
Service - AWS Billing Console Severity Impacted - Inaccurate Estimated Billing Data" Update as of 7:53am PDT: "The rollback of a recent change did not resolve the issue and we are continuing to investigate multiple mitigation paths. Estimated bill updates remain paused." >Estimated bill updates remain paused Wait what if someones actually getting usage spiked 117 billion us dollars. Eat that GDP of Kuwait! But yes I have never scrambled so hard to try to get on the phone with someone at AWS in my life. Terrifying 10 minutes until I found that banner on the support page. It should be front and center on the dash, not hidden away. And in yellow. Mine was 10 trillion today. At first I thought it was a lot, but then I realized its still smaller than the US national debt, so it cant be that bad. For anything below a Trillion, you should just take it out petty-cash. </sarc> My sympathies -- I know I would be overcome with panic in such a situation. Cynically I wonder if this has an outcome as an unintentional (or intentional) anchoring exercise for future cost increases My guess is that it's because of some vibe-coding stuff! We are using LLMs to write code, validate code and test the code ! What can go wrong ? If AWS was a predatory mobile gacha game, we'd get 300 apology gems as credit to our accounts for this mixup, to help us in our rolls for the next 3-letter acronym they release. Do the right thing for the players, Matt! How do we know if our bills were ever right if this made it into production? That's the neat part, you don't! Well, they publish unit prices for everything, so you could just get to counting. Whenever I've had to do cost estimates, you estimate how much AWS resources you need and then times that by the unit price. 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. I 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 Is it even possible to audit the cloud pricing? They just give us a number and we pay. On AWS, you can enable CUR (cost and usage reporting) and get detailed, line-item billing figures that you can audit. And naturally, companies like Cloudability [now Apptio] and others have sprung up to do parts of this for you [at a fee, of course...] https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur... I'm sure other cloud vendors have similar functionality (because they need this on the back end to do their own billing anyway). It was over $500k in the email I got. Not a fun experience. My hands were trembling. Makes you wonder - what if there really would be an incident where some massive amount of traffic got routed to your infrastructure by some heavyweight player? Say Wikipedia accidentally switches their IP to your CloudFront? Would you really be on the hook for $500k? Well, even if AWS tried to charge my credit card on file for $500k, it would definitely not go through. Then they’d probably either forgive your bill or just ban you, since I imagine the threshold for taking people to court is fairly high. logged in this morning to find a bill of $595 Billion... heart rate went through the roof... then I noticed the open issue, phew! nice one guys... you got me there... But with AWS costs rising anyway (not by that much but OK), I'm probably not the only one to start reconsidering their cloud strategy. I think this might have just pushed me over the edge. Even though it's just a bug, being charged $595B on a platform that is known to cost spike, reminds us that we're not in control of the platform, or our company's expenses. same here, I am still in shock. took me 10 minutes to find the 'operational issue' message in the dashboard. longest 10 minutes of my life. Can you not set spending limits in AWS? No you can't. Spending limits imply realtime billing backend flows and they also imply deleting all your data so that you don't pay for storage. I heard this false justification already in 2007, in spite of many customers asking for it. Incidentaly, smaller competitors solved this issue decades ago, while the big cloud decided it is more convenient never to implement it. Realtime billing seems entirely within the abilities of AWS. "Limits except for Storage" seems even easier - I don't think I've ever heard of a storage-based billing story, although I'm sure one or two exist Storage-based billing is huge, unless you mean something other than “places that make you pay for storage separately”. Also many places I’ve worked, storage is a huge part of the spend but that depends a lot on what you do. e-commerce doesn’t use a ton of it, but if you handle user-generated content or do any kind of training (LLM, computer vision, etc) then you can very much end up in a place where storage becomes a top line number for infra spend. GitHub pre-Copilot was probably like that. They host a shitload of data, most of which is just at rest the majority of the time. Storage and networking are probably the majority of their infra costs. What is a storage-based billing story? Once upon a time in a cloud kingdom far, far away a big, beautiful bill was issued based on storage causing much disconcertion. Etc. Storage could switch to read only. That would mean an outage but that is still better than going bankrupt and teach you a thing or two about monitoring. Not only can you not set limits, even the alarms are not real time. So it is entirely possible to get on the hook for terrifying amounts of money and not know until it's all too late. somewhere a junior dev at AWS just learned their billing dashboard has been off by a factor of a billion and is currently having the worst shower of their career Wow. As a side effect, this outage is handing Corey Quinn material for the next 4 years of AWS shitposting. No longer is NAT Gateway the prime target. Yes, I've got an estimated bill of $4bn. Probably related to the ongoing "Inaccurate Estimated Billing Data" incident? I just invested ALL my money into AMZN cause next earnings report will be FIRE :) Does the affiliate program still work for AWS? When do I get my referral fee? And to think the federal government claims inflation is in the single digits this year! Aw man I was hoping to punk my manager but our cost estimates are unaffected. AWS revenue for 2025 was $128.7 billion, so I'd say probably a bug. It's a good job it was off by such a large amount, or I might have panicked instead of writing it off as a phishing attempt. I had an email saying my $7.50 budget had been exceeded with an actual cost of $3bn. I was actually in the toilet when I got an email I owe them $36,869,876,146.51. I literally just shit myself. I got one for 8 billion while I was eating lunch. Thankfully I managed to not vomit. A couple of relevant links:
- AWS Status Page: https://health.aws.amazon.com/health/status
- Reddit Thread: https://www.reddit.com/r/aws/comments/1uyuaw7/help_my_bill_s... Will wait for the RCA, the update says that they will resort to last known estimate as of 15 July. I’m guessing that would imply that the bug is at a lower level, write or an ingestion path. Imagine the chaos if, as people sometimes suggest should happen, AWS shut down running instances in accounts that exceeded a billing threshold.. $44 trillion over here, at least our bill was so outrageously high that I just laughed 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. hmm, if these estimates of Amazon profit for the next quarter are correct Bezos is set to become a trillionaire! Take that Musk!! do you see cost ever day for the month of July or just the last day? I also have billions of dollars in cost explorer The new data centers are more expensive: ACTUAL Amount: $1,046,294,123,330.95 In my 30s, I almost had a heart attack too. I got a notification saying that my cost budget had been increased to one million dollars... Just got a budget alert that I owe $286,486,223.88 on a hobby aws account, almost got a heart attack. This is a strong argument to either self host or work really hard to be cloud agnostic. I have $13,034.40, while not having used AWS for the last 8 months. Not as much but still crapped my pants Same here. Usually $0.15 per month, current bill is $15.4 billion. I went from 0.03€ to $8B. Not only did your cost spike, it changed currency and went from postfix to prefix! I understand people complaining about large bills, but this is over the top! This is just Anthropic reaching out to their customers for help with their AWS bill. The panic was real. We read about keys getting stolen all the time. Was about to nuke my set up too. Mine is showing $241,946,798,744.75. I know it will be reverted, but for a brief minute there I suspected someone compromised my account and triggered rust rewrite of everything using thousands of agents via Bedrock :) Phew. To 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. Glad I saw this. Mine said I racked up $400B yesterday. My usual spend is $15. Maybe this is a new strategy to scare people into finally locking down their old, unused AWS accounts. It sure worked for me! “Due to a rounding error” or a buffer overflow, you now owe INT_MAX to BaldGuyCloudService. Yeah, this most certainly is bad code wrapping around a value. AWS will post a notice soon if they haven’t already. I got 109 billion - am I the winner? Looks like you are the biggest shareholder. Well, going by the popular saying: “You own AWS now”. I'm disappointed I only got a bill for $28M, need to work harder on burning money. Seriously though I thought my life flashed before me Yeah, small timers, I only got $4,4T. How will I finance this? MMT! Unfortunately, it's only Amazon that can issue bills backed by that debt, not the GP. $28m actually seems worse. If I wake to a $100b bill, that’s obviously a mistake. If I wake up to a bill in the millions then my first thought would be “oh no what did I do wrong, this will ruin my life” Obvs have created an urgent AWS support ticket. I think I would have just waited to see what happened when AWS tried to hit my credit card for $1,700,000,000. When do you ever get that opportunity? I had Hermes managing mine, and it made a partial prepayment to help smooth out the bump in my account balance. Unfortunately Billing Support say my $17.4B refund may take up to 10 calendar days to be processed. yeah.. i just to a daily cost alert.. it was only 23 trillion dollars this month. i thought, hmm seems kind of high this month. This generation is too entitled! He should some learn responsibility by paying the full amount; otherwise Amazon should delete his services/data. Consequences! If its less than 2 billion is likely to be real :-)
I would relax only if its in the trillions ... AWS has become the uber employer: before AWS, you just had regular employers steeling employee wages bit by bit by forcing work, skipping breaks, etc. All hail the new generations of our uberployers. My personal photo backup S3 account, with a budget limit of $10, now going to cost me .... $1,299,988,247,332.56! That was a fun set of emails to wake up to, figured they had to be phishing for how outrageous of a number it was. But nope! Fun little incident they've got going over there. AMZN Q2 numbers are in, and it turns out they're going to Goldman Sachs the AI bubble. Imagine it not being a bug... As the famous saying goes: If you owe the bank a million dollars, you have a problem. If you owe the bank a billion dollars, the bank has a problem. You really should get your spending under control. Unfortunately unless you become one of the real people class through a large lottery, it sounds like you owe the rest of your life to AWS until you can pay off your debts for being so careless. Uhh class action incoming? $34,909,930,575.09 over here. What would your damages be? They’re not actually going to charge your credit card for 34 billion. 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 hope they send out some free credits at least. I imagine quite a few people got a real fucking scare today. They haven't even sent out any corrections yet. This is probably going to push me to completely close a couple of AWS accounts I setup when doing training courses so I could get certified (mandatory requirement from my work). I'm not currently running anything and have no plans to at the moment. I've always had a mild dread that I'll suddenly get a bill for more than $0.00. If AWS can goof in a way that causes obviously massive bills (like today), what's to say they can't goof in more subtle ways and start charging small additional amounts that many people may not notice and just pay it. I got estimated costs of $56.something billions. Usually ~$100/month. My heart rate currently still sits at around 160 bpm. Motherfuckers. Clearly they weren't tokenmaxxing hard enough or weren't using the latest models /s. What an absolute joke. All just so that line goes up. As if their fees weren't high enough vs. alternatives (especially egress).
And I'm sure the pro-AI crowd will keep saying we're luddites for not loving this clearly revolutionary and disruptive tech. Don't worry. With so much debt banks start to treat you with respect. /S Honestly, I would worry more about estimated billing that seems plausible in general, but is way to high for you personally.
These ridiculous amounts? Not so much. I got freaked out by the mere fact that I got a billing alert, since getting one would require my monthly spend to have suddenly exploded. In unrelated news I just hit my target for S3 revenue (projections). Promotion meeting locked in for tomorrow (fastest in the companies history), looking forward to being a L2 Amazon employee. Of course, this is only considered an error if the account is unable to pay. /s
yuchen20 - 5 hours ago
root-parent - an hour ago
ibejoeb - an hour ago
This is invoicing? If ever there was a domain that was purely deterministic, you'd hope it was invoicing. In this role you will:
- Design and build agentic AI systems that analyze, generate, and validate...
- Build agentic architectures that compose specialized AI agents dynamically...
- Build AI-driven continuous validation frameworks powered by agentic workflows and large language models that autonomously manage...
cliglot - 18 minutes ago
root-parent - an hour ago
jdiff - 39 minutes ago
serf - 15 minutes ago
sebmellen - an hour ago
root-parent - an hour ago
wbl - 25 minutes ago
ghurtado - 32 minutes ago
rcleveng - an hour ago
wglass - 23 minutes ago
aerhardt - an hour ago
Nicook - 37 minutes ago
unethical_ban - 25 minutes ago
The_Blade - 38 minutes ago
RIMR - 41 minutes ago
IAmGraydon - 8 minutes ago
lukaslueg - 6 hours ago
VulgarExigency - an hour ago
ghurtado - 29 minutes ago
leugim - an hour ago
hansvm - an hour ago
stefan_ - an hour ago
raverbashing - an hour ago
root-parent - an hour ago
27183 - an hour ago
daft_pink - 4 minutes ago
bobbiechen - an hour ago
ruddct - 5 hours ago
fatnoah - an hour ago
Imustaskforhelp - 38 minutes ago
xp84 - 22 minutes ago
danlitt - an hour ago
sajithdilshan - an hour ago
browningstreet - an hour ago
hedora - an hour ago
xp84 - 30 minutes ago
ofjcihen - 29 minutes ago
browningstreet - 18 minutes ago
mawadev - 2 minutes ago
szge - 8 minutes ago
lelandfe - 8 minutes ago
rboyd - 4 hours ago
tedggh - an hour ago
drew870mitchell - an hour ago
srdjanr - 39 minutes ago
ButlerianJihad - 5 minutes ago
dawnerd - an hour ago
myself248 - 7 minutes ago
wewewedxfgdf - 5 hours ago
TedDoesntTalk - 2 hours ago
ambicapter - 2 hours ago
27183 - an hour ago
bobson381 - 11 minutes ago
sscaryterry - 5 hours ago
ainiriand - an hour ago
roskoalexey - 3 hours ago
xp84 - 12 minutes ago
pqvst - 6 hours ago
everforward - an hour ago
TrickyRick - 7 minutes ago
krawat3 - 4 hours ago
zengineer - 6 hours ago
saghm - an hour ago
gomid - 3 hours ago
bradhe - an hour ago
xp84 - 18 minutes ago
glenstein - 4 hours ago
philipallstar - 6 hours ago
the_real_cher - 4 hours ago
paulddraper - 2 hours ago
egeozcan - an hour ago
mrtksn - 5 hours ago
jumperabg - 5 hours ago
qrios - an hour ago
berkes - an hour ago
galonk - 5 minutes ago
everforward - an hour ago
ardacinar - 36 minutes ago
pcarmichael - 5 hours ago
Polizeiposaune - 18 minutes ago
masafej536 - 5 minutes ago
pfshort - 4 hours ago
dgrin91 - 3 hours ago
tanseydavid - 13 minutes ago
dv_dt - 5 hours ago
nblgbg - 27 minutes ago
btown - 18 minutes ago
cryo32 - an hour ago
ahoka - an hour ago
Hamuko - an hour ago
scrapcode - an hour ago
iamrik9 - 6 hours ago
whatever1 - 16 minutes ago
sokoloff - 6 minutes ago
TekMol - 6 hours ago
Hamuko - 5 hours ago
marksk - 5 hours ago
sshine - 5 hours ago
dirkk0 - 5 hours ago
charles_f - 4 hours ago
inigyou - 4 hours ago
benterix - 2 hours ago
handoflixue - 3 hours ago
everforward - an hour ago
minitoar - 2 hours ago
kgwgk - an hour ago
prmoustache - 41 minutes ago
perching_aix - 29 minutes ago
luciana1u - an hour ago
nixgeek - an hour ago
Sheepzez - 5 hours ago
bdangubic - 9 minutes ago
hedora - 37 minutes ago
hedora - 41 minutes ago
rtkwe - 44 minutes ago
paulbjensen - 4 hours ago
mjmasn - 2 hours ago
mlitwiniuk - 6 hours ago
Hamuko - 6 hours ago
andystanton - 6 hours ago
abkolan - 3 hours ago
anon49584 - 7 minutes ago
durron - an hour ago
compounding_it - 4 hours ago
bryanrasmussen - 2 hours ago
ohnoooooooooo - 24 minutes ago
anibal-sanchez - an hour ago
anzovec - 4 hours ago
csunbird - 6 hours ago
jimbokun - an hour ago
lsdafjasd - 5 hours ago
meraku - 6 hours ago
Hamuko - 6 hours ago
sshine - 5 hours ago
axus - 2 hours ago
abkolan - 3 hours ago
princetman - 6 hours ago
hypfer - an hour ago
aweiland - 4 hours ago
AegirLeet - 6 hours ago
reactordev - 4 hours ago
ninjin-carh - 6 hours ago
atmosx - 4 hours ago
bknight1983 - 4 hours ago
danousna - 4 hours ago
rodeduivel - 4 hours ago
marcosdumay - an hour ago
MichaelNolan - 4 hours ago
reaperducer - an hour ago
kvcm - 4 hours ago
cmollis - 5 hours ago
Executor - 3 hours ago
tcp_handshaker - 2 hours ago
cyanydeez - 5 hours ago
jameskilton - 3 hours ago
mapt - 4 hours ago
pelagicAustral - 4 hours ago
Sebb767 - 4 hours ago
lovich - 4 hours ago
rucury - 6 hours ago
akerl_ - 5 hours ago
rucury - 5 hours ago
akerl_ - 5 hours ago
Hamuko - 5 hours ago
fian - 4 hours ago
tlovage - 6 hours ago
throwaway43871 - 16 minutes ago
GuestFAUniverse - 5 hours ago
Hamuko - 5 hours ago
blitzar - 4 hours ago
rf15 - 44 minutes ago