Amazon Overcharges Users Billions Beyond What They Owe

Many people feel the pinch of rising costs in today’s economy. If you’ve ever stood at the checkout line feeling like you’re being robbed, you can relate. Now, imagine discovering you owe billions—or even trillions—more than expected for web hosting services. That would certainly jolt anyone from their financial stupor.

Recently, users of Amazon Web Services (AWS) experienced a shocking billing error:

I just saw $1.5 trillion on my AWS bill and my soul left my body https://t.co/EgfQKJTHVl pic.twitter.com/L0gXYbDio7

— Bharath (@Bharath_uwu) July 17, 2026

Bharath, a user from India, shared a staggering bill amounting to $1,499,659,180,107, exclaiming, “my soul left my body.” This outrageous total indicates a 744,728,201,771% increase from the previous month, suggesting his last bill was around $200.

A marketer named Dan Harvey, working for a nonprofit educational organization in the U.K., recounted a similar shock. His bill skyrocketed from just 43 cents last month to $7.8 billion this month, and the month wasn’t even over yet. Harvey told the Guardian that he had to contact tech support to dig into the issue. Unfortunately, Amazon did not respond to the Guardian’s request for comments.

Amazon has since addressed the issue. They stated that on July 16 and 17, customers received incorrect budget and cost anomaly alerts and witnessed inflated cost estimates in the Billing and Cost Management Console and the Cost and Usage Reports. Amazon assured users that these amounts were inaccurate and did not impact actual invoices, and that everything has now returned to normal.

An update on the AWS service health dashboard clarified the situation. On July 16, a problematic “configuration change” was made in the AWS billing system. This system depends on unit conversion data to determine line item charges. the change led to failures in updating the unit conversion data, which caused inflated line item costs that propagated through the Billing and Cost Management console, triggering the erroneous budget and cost anomaly alerts.

The health dashboard logs indicate that AWS worked on a solution for about two days before resolving the issue completely.