AWS Billing Glitch Shows Users Trillion-Dollar Charges Across Multiple Countries

Thousands of Amazon Web Services (AWS) users worldwide saw estimated bills in the trillions of dollars after a technical glitch affected the AWS billing system. On July 16 and 17, users reported seeing incorrect estimated charges, with some bills reaching as high as $1.5 trillion. The issue led to widespread confusion and concern among developers, students, charities, and small businesses across India, the UK, Europe, and the US.

Key Highlights

• AWS users worldwide saw estimated bills up to $1.5 trillion due to a technical glitch.
• Amazon confirmed the issue only affected estimated billing data and not actual invoices.
• The glitch resulted from a faulty configuration change in AWS billing calculations.
• Users in India, UK, Europe, and US reported seeing inflated charges and incorrect alerts.

Global Impact of AWS Billing Error

Bharath, an AWS user from India, posted a screenshot on X showing an estimated monthly cost of $1,499,659,180,107. His account also displayed an increase in estimated spending of 744,728,201,771 percent, despite no actual rise in cloud usage. The post quickly gained attention, with many AWS customers sharing similar experiences online.

Amazon confirmed that the issue stemmed from a technical problem affecting the AWS Billing and Cost Management Console and Cost and Usage Reports. The company stated that customers received incorrect budget alerts and anomaly detection notifications, but actual invoices remained unchanged. Amazon apologized for the confusion and assured users that no action was required while engineers worked to resolve the problem.

Examples of Affected Users

The glitch was not limited to India. In the UK, Dan Harvey from the educational charity Learning Through Landscapes received an alert for a $7.8 billion bill, compared to the usual 43 cents. In Delhi, a student named Sachin, who typically spends $1.28 per month, saw his estimated bill jump to $10.9 billion. Another UK customer reported a $245 billion bill, while several Reddit users posted screenshots of charges exceeding $7 trillion.

Social media platforms filled with memes and jokes as users reacted to the unexpected figures. One X user wrote, "Good morning to everyone enjoying their heart attacks," while another questioned AWS, "What did I even do?" AWS Support acknowledged the incident, responding humorously to one user about the "slight miscalculation."

Technical Cause and Resolution

AWS explained that a faulty configuration change prevented updates to unit conversion data used in estimated billing calculations. This error caused line-item costs to be massively inflated, resulting in incorrect budget alerts and anomaly notifications. To fix the issue, AWS paused billing calculations, rolled back the problematic configuration, and restored normal estimated billing data after about two days.

Amazon reiterated that no customers were overcharged and that the incorrect figures did not affect actual invoices. The company emphasized that the problem only impacted estimated billing data and not real charges.