technology
AWS Billing Console Displayed Incorrect Estimates for Some Customers Before Fix
The error began late Thursday and affected estimated billing data across the service. Amazon identified a unit pricing issue in its computation subsystem and mitigated it by Friday morning.
Jul 17, 3:50 PM·1m read3 sources
Display errorSystem failure
theregister.comAudio version
Tap play to generate a narrated version.
Developing·Limited corroboration so far. This page will refresh as more sources emerge.
The AWS billing console began displaying incorrect estimated billing data at 10:38 pm EDT on July 16, 2026. The root cause was an issue with unit pricing within the estimated billing computation subsystem. Amazon began investigating the problem approximately six hours after it started.
The company rolled back a recent change to the billing computation subsystem and paused estimated billing computations. Amazon stated that the billing estimates do not reflect actual usage and charges. The issue was characterized as global, and the company disabled its estimated billing feature while apologizing for the confusion and concern.
Bill Radjewski of CollegeFootballData.com received an alert showing over $1.5 billion in usage fees and a projected August 1 bill of upwards of $3 billion. His monthly AWS spend had never exceeded $0.02 over more than six years of account history. Other customers reported estimated bills of $22 billion, $75 billion, and $110 billion.
One Reddit user reported an AWS cost and usage overview showing $7.1 trillion in service fees since July 1, 2026. Affected customers saw estimates ranging from a few million dollars to hundreds of millions of dollars. Amazon confirmed it began seeing inaccurate billing data as of late Thursday.
The rollback of a recent change did not resolve the billing issue. Amazon stated it had identified the root cause and mitigated the underlying issue by around 10am Friday, July 17, 2026. The issue was expected to last several more hours from the time of that update, with no customer actions required.
Amazon spokesperson Aisha Johnson referred inquiries to the AWS Service Health Dashboard. The company said the issue should be resolved by the weekend of July 18-19, 2026.
