AWS Trillion-Dollar Glitch
AWS Billing Glitch Projects Trillions in False Costs, Causing Alarm but Not Affecting Actual Charges
Anonymous
Key Points
1
AWS identified the root cause as a unit-pricing error within the estimated billing computation subsystem, and warned that full recovery would require recomputing estimated charges across affected accounts, a process expected to take several hours.
2
The incident produced alarmingly high projected bills for real customers, including a charity that reported a $7.8 billion estimate and elsewhere figures such as $1.5 trillion, highlighting the surreal scale of the glitch.
3
AWS stressed that the inflated projections were limited to estimated billing data from Cost Explorer and the Billing and Cost Management Console and did not reflect actual usage or imminent invoices.
4
The outage affected Cost Explorer and related billing tools, with AWS directing affected customers to the AWS Health Dashboard for updates; the issue began around 7:38 PM PDT on July 16 and remained under investigation into the next day as engineers worked to resolve it.
AWS customers around the world opened their billing dashboards this week to find estimates in the trillions of dollars — for cloud services that normally cost pocket change. One charity reported a projected bill of $7.8 billion, while some users saw figures as high as $1.5 trillion, according to The Guardian. Amazon confirmed the glitch was real, but stressed that no one would actually be charged.
The root cause was a unit-pricing error inside AWS's estimated billing computation subsystem, which powers tools like Cost Explorer and the Billing and Cost Management Console, TechCrunch reported. AWS said the bug affected only projected cost data — not real usage or actual invoices. Engineers began working to fix it around 7:38 PM PDT on July 16, but warned that full recovery would take several hours as estimates had to be recalculated across all affected accounts.
How a Pricing Error Produced Trillion-Dollar Estimates
AWS's billing tools use a subsystem to estimate what customers will owe at the end of the month. That subsystem pulls unit pricing — the cost per hour, per gigabyte, or per request — and multiplies it by usage. A bug caused those unit prices to be wildly wrong, The Register reported. The result was estimates inflated by many orders of magnitude, turning a $5 monthly bill into a multi-billion-dollar projection.
TechBuzz noted the error hit enterprise accounts across multiple regions. AWS confirmed the problem was limited to the estimated billing layer and did not touch the systems that track real usage or generate actual charges. In plain terms: the meter was broken, but no one was actually being overbilled.
Customers Saw Surreal Bills for Everyday Services
The numbers were startling. The Guardian reported one user's monthly AWS subscription — normally less than the price of a coffee — jumped to $1.5 trillion in their dashboard. A charity saw a projected bill of $7.8 billion. The Register cited one specific example of a $2.5 billion estimate generated by the glitch. These were not edge cases — the bug spread across accounts worldwide.
For many businesses, Cost Explorer is a critical budgeting tool. Teams use it daily to forecast spending and catch unusual charges. Seeing a trillion-dollar projection — even a clearly wrong one — caused real alarm, especially for finance teams and nonprofit organizations with tight budgets and strict spending controls, according to Whalesbook.
AWS Confirms No Real Charges, Promises Full Fix
Amazon moved quickly to reassure customers. The company confirmed that the inflated figures reflected only estimated billing data — not actual usage, not unauthorized activity, and not real invoices. AWS directed affected customers to the AWS Health Dashboard for live updates as engineers worked to resolve the issue, TechCrunch reported.
The fix required recomputing estimated charges across every affected account — a time-consuming process. AWS warned this would take several hours to complete. The incident highlighted how much businesses rely on billing estimates to manage cloud costs, and how disruptive even a non-financial glitch in those tools can be, according to Whalesbook.
Sentiment
Mostly NegativeNEGATIVENEUTRALPOSITIVE
Publishers
11
Articles
1
Reach
12
A
AnonymousAuthor