A Billing Glitch Told Some AWS Customers They Owed Billions. They Don't.
Amazon says a bug in its cloud billing system generated wildly inflated cost estimates, and the company is still working to fix it.
Some Amazon Web Services customers opened their billing dashboards this week to find a number that made their stomachs drop: bills in the millions, or in at least one case, close to $2.5 billion. Amazon says none of it is real.
The company confirmed Friday that it's working to fix a bug in the AWS billing portal that generated wildly inaccurate cost estimates for some customers, according to TechCrunch. Amazon first noticed the bad billing data late Thursday, and the problem traces back to what the company describes as its billing computation subsystem, the internal machinery that tallies up usage and turns it into a dollar figure on a customer's account.
The strange part is that Amazon's usual fix didn't work. Engineers rolled back the recent change believed to have caused the issue, standard practice when something breaks after an update, but the rollback failed to solve it. That detail, disclosed on Amazon's status page, suggests the bug is more tangled than a simple bad deployment.
For customers staring at eye-watering totals, Amazon has one clear message: don't panic. The company said the numbers showing up in accounts "do not reflect actual usage and charges." In other words, the bug is cosmetic in the sense that it's generating phantom invoices, not actually charging anyone for services they never used.
That's cold comfort if you're the person who logged in and saw a nine-figure or ten-figure number attached to your company's name. Screenshots circulating on Reddit show the range of damage: one AWS customer was quoted an estimated bill of roughly $2.5 billion for the month. Others reported figures anywhere from a few million dollars up to hundreds of millions. For businesses that rely on AWS to run everything from websites to backend infrastructure, seeing a bill that dwarfs their entire revenue is the kind of thing that triggers immediate panic, emergency calls to finance teams, and probably more than a few frantic Slack messages to IT.
Why a billing bug is scarier than it sounds
AWS underpins a huge share of the internet's infrastructure, and its billing system is built to handle usage-based pricing at a massive scale, tracking everything from compute time to storage to data transfer down to fine-grained units, then converting all of that into a monthly charge. When that system misfires, the result isn't a typo on an invoice. It's an estimate that can look like a company owes more money than most businesses will ever generate in a lifetime.
Amazon hasn't detailed exactly what went wrong inside the billing computation subsystem, and a company spokesperson did not immediately respond to a request for comment from TechCrunch. What is clear is that this wasn't a brief blip. As of Friday morning, Amazon was still working the problem, and its own status page indicated the issue was expected to persist for several more hours.
What customers should actually do
Amazon's guidance boils down to: these numbers are wrong, ignore them. The company has been explicit that the inflated figures don't represent real charges tied to actual usage. For now, affected customers are left watching the status page and waiting for their dashboards to return to normal, rather than taking any action based on the erroneous totals.
The episode is a reminder of how much trust businesses place in cloud providers to get the accounting right, not just the uptime. AWS customers don't just depend on Amazon to keep servers running, they depend on the billing layer to accurately reflect what they're using, since that data feeds directly into corporate budgets, financial planning, and cash flow decisions. A glitch that inflates estimates into the billions, even briefly and even if never actually charged, is the kind of thing that erodes confidence in a system companies otherwise treat as background infrastructure they don't have to think about.
Amazon says it's still chasing down the root cause. Until it's resolved, AWS customers checking their accounts should expect the possibility of more phantom numbers before the dashboard settles back into something believable.
