Amazon Web Services customers opened their billing dashboards and email alerts to find charges that looked less like cloud usage and more like sovereign debt. AWS said the figures were wrong, caused by a global problem in its estimated-billing system, and told customers no action was required.
The incident matters because AWS billing is where developers, small site operators, and companies watch for runaway infrastructure costs. A bad number there can trigger panic fast, especially when the number has 10 or 12 digits and the customer normally spends pocket change.
Bill Radjewski, who runs CollegeFootballData.com, told WIRED he received an AWS email saying his account had already accumulated more than $1.5 billion in usage charges and was projected to owe more than $3 billion on an August 1 bill. Radjewski said his AWS account has been open for more than six years and that his monthly spending had never gone above $0.02. He also shared screenshots with WIRED showing each of his three most recent AWS invoices at $0.01.
Other AWS customers posted similar complaints in replies to the AWS Support account on X, according to WIRED. Users reported estimated bills of $22 billion, $75 billion, and $110 billion. One user said AWS had shown a $5 million cost and asked what they had done to cause it. On Reddit, a user posted a screenshot in the AWS subreddit showing a “Cost and usage overview” with $7.1 trillion in charges since July 1.
What AWS says happened
Amazon spokesperson Aisha Johnson directed WIRED to the AWS Service Health Dashboard when asked for comment. The dashboard described the problem as global, though AWS did not say how many customers saw incorrect billing estimates.
According to the dashboard, the AWS billing console began showing bad estimated billing data on Thursday, July 16, at 10:38 pm ET. AWS said it started investigating about six hours later.
AWS attributed the problem to “an issue with unit pricing within the estimated billing computation subsystem,” according to the dashboard. That is the part of the billing machinery that turns metered usage into an estimated dollar figure before the final invoice is produced. AWS did not provide a more specific technical explanation for the pricing error.
In later updates, AWS said it was rolling back a recent change to the billing computation subsystem and trying to restore the “last known good estimated bill computation.” The company also said it had paused estimated billing computations while it worked on the fix.
AWS said the issue should be resolved by the weekend and that customers did not need to do anything. That statement covers the immediate practical question: AWS is saying these are bad estimates, not real bills customers are expected to pay.
The episode is still a reminder of how much trust cloud customers place in opaque billing systems. AWS meters compute, storage, bandwidth, API calls, and plenty of smaller line items. When the math layer misbehaves, the dashboard can turn a one-cent hobby project into a fake trillion-dollar liability before anyone has had coffee.
This story draws on original reporting from WIRED.
