AWS Billing Glitch Sends Customer Invoices Into the Trillions
An issue with unit pricing in the estimated billing computation subsystem has led to inflated fees for some users, with one account showing $7.1 trillion in charges since July 1.
A technical fault within Amazon Web Services’ billing infrastructure has resulted in some customers receiving monthly invoices inflated to billions of dollars. The global error, identified as a problem with unit pricing within the estimated billing computation subsystem, has disrupted financial visibility for users of the cloud computing platform.
Bill Radjewski, who operates CollegeFootballData.com, was among those affected, receiving an email alert indicating he owed more than $1.5 billion in usage fees. Radjewski noted that his account, active for over six years, had previously incurred monthly spends of no more than $0.02, with recent invoices showing charges of just $0.01. He stated that his August bill was projected to exceed $3 billion.
Other users reported similarly inflated figures, including quotes of $22 billion, $75 billion, and $110 billion. On social media platform X, affected customers sought explanations from the AWS Support account, with one user expressing shock at a cost of 5 million USD. Another Reddit user posted a screenshot showing $7.1 trillion in service fees incurred since July 1, a figure that exceeds twice Amazon’s market capitalisation.
AWS characterised the issue as global on its Service Health Dashboard, stating that the billing console began displaying incorrect estimated billing data on Thursday, July 16, at 10:38 PM ET. The company began investigating approximately six hours after the issue started and identified the root cause as the unit pricing error within the estimated billing computation subsystem.
In response, AWS is rolling back a recent change to the billing computation subsystem and has paused estimated billing computations to resolve the global error. The company stated that the issue should be resolved by the weekend and that no customer actions are required at this time. Amazon spokesperson Aisha Johnson referred inquiries to the AWS Service Health Dashboard for further details.
