AWS Billing Glitch Hits Customers With Billion-Dollar Fees
Key Points
- AWS billing console displayed incorrect estimated charges starting July 16 at 10:38 PM ET, with one customer seeing $1.5 billion in fees after 6+ years of $0.01 monthly bills.
- Affected customers reported charges ranging from $5 million to $110 billion, including one user seeing $7.1 trillion in accumulated fees since July 1.
- AWS identified the root cause as an issue with unit pricing in the estimated billing computation subsystem and began rolling back changes, with resolution expected by the weekend.
AWS Identifies Root Cause and Begins Fix
AWS began investigating the issue approximately six hours after it started, ultimately identifying what it called the "root cause" as "an issue with unit pricing within the estimated billing computation subsystem." The company did not specify the precise nature of the pricing unit error. By Friday, AWS announced it was "rolling back a recent change to the billing computation subsystem" and attempting to revert to its "last known good estimated bill computation." The company also stated it had "paused estimated billing computations" across its systems.
Read Next
Meta Reports Q2 Earnings Amid AI Investment Concerns
7 days ago
Nvidia Launches Cybersecurity Initiative for Open-Source AI Defense
8 days ago
In a statement to WIRED, Amazon spokesperson Aisha Johnson directed customers to the AWS Service Health Dashboard for updates without providing additional details. AWS indicated that no customer actions were required and that the issue should be resolved by the weekend. The company characterized the scope of the problem as "global," though it did not disclose the exact number of affected customers.
While AWS has suffered previous outages—including significant regional failures in 2020 and 2021—this represents an unusual incident in which the core billing calculation system itself became corrupted, potentially affecting visibility across millions of accounts simultaneously rather than service availability for specific AWS products.
Related coverage: Meta Reports Q2 Earnings Amid AI Investment Concerns
The incident created particular anxiety among AWS customers because billing errors can trigger automated account suspension or resource termination if charges appear to violate account spending limits. Unlike actual service outages that prevent deployments, billing glitches leave customers uncertain whether their worst fears are real until official clarification arrives.
Some customers took the situation philosophically. One Reddit user in the AWS community responded to the $7.1 trillion charge screenshot with humor, joking that at least they were getting a good rate on compute resources. Others expressed genuine concern about the integrity of AWS's billing systems and whether hidden errors might persist beyond this visible glitch.
Why this matters: If you run services on AWS—whether you're a small startup or an enterprise—your monthly bill directly impacts your business's profitability and operational planning. A billing system that can display errors this severe, even temporarily, raises legitimate questions about whether similar miscalculations could occur in actual charges without detection, and how many customers might have dormant accounts that weren't monitored closely enough to catch such discrepancies immediately.
What This Means
This incident will likely accelerate AWS customer demand for enhanced billing alerts, third-party cost monitoring integrations, and clearer separation between estimated and confirmed charges. Competitors like Google Cloud and Microsoft Azure may use this event in sales conversations, though widespread cloud outages are industry-wide concerns. AWS will probably implement additional validation layers in billing computation systems.
Sources: AP, Reuters, ESPN, Bloomberg, BBC and other international news outlets.
Disclaimer: This article is for informational purposes only. Content is based on publicly available news sources.
