- Customers receive unexpectedly large AWS bills due to a computer error.
- Invoices range from $15 to over $240 billion, shocking even the largest accounts.
- The glitch impacted millions of users worldwide, causing widespread concern and confusion.
What Happened
A recent computer error at Amazon Web Services (AWS), a global leader in cloud computing services, led to customers receiving shockingly large invoices that could be linked back to an issue with unit pricing within AWS's estimated billing computation subsystem. Patrons of the service have been landed with panic-inducing monthly bills running as high as $1.5 trillion for subscriptions that usually cost less than the price of a cup of coffee, affecting users from Bangalore to Bolsover.
The problem stemmed from an issue detected at 3:38 AM UK time on Friday, sending ripples through social media and prompting widespread panic among AWS customers. According to the original source text, Patrons of Amazon Web Services faced bills that were several orders of magnitude higher than their usual charges. For instance, Dan Harvey, head of marketing at the Hampshire-based Learning Through Landscapes charity, found his typical £1 per month bill had skyrocketed to over $7 billion (£5.8 billion).

Another user from Delhi, Sachin, usually pays $1.28 a month but was suddenly billed $10.9 billion. He posted on X asking AWS support to investigate the issue: “Could you please investigate,” he plaintively asked.
Customer Reactions and Widespread Panic
The incident sent ripples through social media as users shared their shock and panic. One user from Bolsover in Derbyshire reported a bill of over $245 billion, prompting Andrea Zuvich, the founder of The Seventeenth Century Lady, to admit she was 'terrified' after receiving her invoice.
Another X user in Maine quipped: “Good morning to everyone enjoying their heart attacks.” These reactions highlight the unprecedented scale and impact of the error. According to the original source text, customers were left stunned by the astronomical figures. For example, Bharath posted on X with a screenshot showing his usage was up 745,728,201,771% from the previous month, equating to $1.5 trillion on his AWS bill.
Technical Glitch Details
The problem stemmed from an issue with unit pricing within AWS's estimated billing computation subsystem. The glitch was first detected at 3:38 AM UK time on a Friday, causing significant concern among both small businesses and large enterprises alike. Amazon acknowledged the confusion and apologized for the issues in their official update.
The company stated: “We strive to be Earth’s most customer-centric company,” but admitted their billing process had failed spectacularly. In response, AWS quickly shut down the bill estimation system and initiated an investigation that took over an hour and a half. The company reported: “an issue with unit pricing within the estimated billing computation subsystem” as the cause of the problem.
Resolution and Next Steps
AWS promised to resolve the issue by recalculating estimated billing data, but the sheer scale of the task presented a significant challenge for the tech giant. The incident underscores the importance of robust systems in managing financial transactions and highlights the potential impacts when such systems fail.
As AWS works to correct the situation, customers are left wondering about future safeguards against similar errors. The original source text emphasizes that the crazy figures started to be displayed on the AWS billing and cost management console at 3:38 AM UK time, causing immense concern among users around the globe. The company stated in an update: “We expect full resolution to take multiple hours as we work through recomputing the estimated billing data.”
The incident has raised serious concerns about the reliability and accuracy of AWS’s billing system, leaving many users questioning how such a significant error could go undetected for so long. The situation serves as a stark reminder of the potential pitfalls in complex cloud computing services and the need for stringent checks and balances to prevent similar issues from arising in the future.
Source: The Guardian





