AWS Billing Bug Sends Estimated Charges Soaring to $2.5 Trillion, Panicking Customers

AWS customers woke up Friday to estimated billing emails showing charges ranging from hundreds of millions to $2.5 trillion, the result of a unit pricing error in the AWS Billing Console's estimated billing computation subsystem. Amazon confirmed the bug and said the displayed figures do not reflect actual usage or charges.

One Reddit user whose monthly charges totaled $0.19 last month received an estimated bill of nearly $2.5 billion. Other users reported estimated monthly charges between $126,000 and $2.5 trillion, triggering widespread panic before the error was identified.

Root cause and response timeline

Amazon identified the root cause within 90 minutes of the first reports, describing it as an issue with unit pricing within the estimated billing computation subsystem. The company paused estimated bill updates to prevent the inflated figures from increasing further and began recomputing all billing data. Corrected amounts are expected to appear by Saturday, July 18 at noon Pacific time.

• The bug affected estimated billing emails sent to a subset of AWS customers on Friday morning.
• Amazon stated that the displayed billing estimates do not reflect actual usage and charges.
• One user with two S3 buckets containing a few megabytes of data saw a half-billion-dollar forecast.
• Another user panicked and destroyed all resources on their account before realizing the error.
• AWS has committed $1 billion to forward-deployed AI engineers last week, highlighting the scale of infrastructure spending.

Implications for cloud billing reliability

The incident comes a day after a separate AWS CloudFront outage served errors instead of websites, compounding concerns about the reliability of AWS services. Cloud infrastructure is handling unprecedented spending volumes as AI demand pushes monthly compute bills into the hundreds of millions for individual customers, making billing system reliability a higher-stakes problem than it was when the largest bills were measured in thousands.

Amazon has not disclosed how many customers were affected or whether any actual charges were incorrectly applied. The company expects the recomputation to restore accurate estimates by Saturday noon Pacific time. AWS users are advised to monitor their billing consoles for corrected figures and to contact support if discrepancies persist.