A glitch in Amazon Web Services’ billing system caused some customers to believe they owed the cloud giant trillions of dollars, according to a report from WIRED. The error, which affected customers globally, stemmed from an issue with unit pricing in the estimated billing computation subsystem.
The Glitch and Its Scale
According to WIRED, the billing console began displaying incorrect estimated billing data on Thursday, July 16, at 10:38 PM ET. Bill Radjewski, who runs CollegeFootballData.com, received an email alert showing he had racked up more than $1.5 billion in usage fees, with his August 1 bill on track for upwards of $3 billion. Radjewski’s account had never exceeded $0.02 in monthly spend over six years; his three most recent invoices were each $0.01.
Other customers reported similarly shocking quotes: $22 billion, $75 billion, and $110 billion. One Reddit user posted a screenshot of their current “Cost and usage overview” showing $7.1 trillion in service fees since July 1 — more than twice Amazon’s market cap, WIRED reported.
Customer Reactions
Radjewski told WIRED, “I've had this account for 6+ years and in that time my monthly spend has never exceeded $0.02.” He shared screenshots of his invoices. On X (formerly Twitter), users replied to the AWS Support account with their own inflated amounts. “Blud why did you hit me with a cost of 5 million USD what did I even do,” one user wrote. “Please explain man my heart will explode.”
A table comparing normal spend to erroneous bills illustrates the magnitude:
| Customer | Normal Monthly Spend | Erroneous Bill Shown |
|---|---|---|
| Bill Radjewski | $0.01 | $1.5B+ (tracking $3B) |
| Other customers | Unknown | $22B, $75B, $110B |
| Reddit user | Unknown | $7.1T |
Amazon’s Response and Root Cause
Amazon spokesperson Aisha Johnson referred WIRED to the AWS Service Health Dashboard, which characterized the issue as “global.” The dashboard stated that the company began investigating the problem about six hours after it started. The root cause was identified as “an issue with unit pricing within the estimated billing computation subsystem,” according to the dashboard. AWS did not specify the exact nature of the issue.
The company is “rolling back a recent change to the billing computation subsystem” and attempting to revert to its “last known good estimated bill computation,” WIRED reported. AWS also said it “paused estimated billing computations.” The issue is expected to be resolved by the weekend, and “there are no customer actions required at this time,” the company wrote.
Implications for Enterprise Customers
For enterprise customers — including those in supply chain and logistics who rely on AWS for cloud infrastructure — this glitch highlights the critical importance of accurate billing systems. While no actual charges were incurred, the incident caused confusion and alarm. Companies that depend on AWS for cost management and budgeting may need to reassess monitoring processes. The error, though temporary, underscores the potential for cloud billing systems to generate misleading data, which could disrupt financial planning and operational decisions if not quickly corrected. As AWS works to restore normal billing, customers are advised to verify their charges once the system is stable.
Sources:
