July 20, 2026
The Day AWS Accidentally Billed the World Trillions
At 3:38am UK time on 17 July, a major glitch impacted Amazon Web Services’ (AWS) billing system. For a few anxious hours, some of its customers thought they might have accidentally bankrupted a small country.
A Hampshire charity that normally pays under a pound a month for a schoolgrounds audit app opened its account to find a bill for $7.8bn. A student in Delhi, usually charged $1.28, was asked to explain a leap to $10.9bn. In one case reported on social media, a user’s dashboard showed a monthly usage increase of 745,728,201,771%.
None of it was real, however. An internal tool that estimates what each AWS account owes had applied the wrong price to real usage data. This threw every subsequent calculation off by orders of magnitude. Engineers found the fault within about ninety minutes and switched off the estimation tool while the real figures were recalculated.
AWS confirmed there was “an issue with unit pricing within the estimated billing computation subsystem.” It added that the billings:
“…do not reflect actual usage and charges.”
That distinction mattered little to the people staring at the numbers tin real time, though. Dan Harvey, Head of Marketing at the Hampshire-based charity Learning Through Landscapes, was one of them.
“I almost had a heart attack when I received an email alert from Amazon Web Services with the billing for our charity’s school grounds audit app, which usually costs us less than a pound per month.” Harvey told The Guardian.
The bug spread wide. Similar reports arrived from customers across South Asia, continental Europe and the UK, most describing the same pattern. A modest, predictable monthly charge was replaced overnight by a number with more zeros than most people will ever need to count. Amazon acknowledged the alarm the figures had caused and said a full fix would take several hours as it worked through recomputing the billing data. By the following day, the dashboards were showing something closer to reality again.
What the Market Is Reading Into the Billing Glitch
On its own, this is a minor operational hiccup that cost Amazon an afternoon of bad headlines and nobody a cent. Its timing is arguably what makes it worth a second look. The European Commission is currently weighing whether to designate AWS, along with Microsoft Azure, as a gatekeeper under the Digital Markets Act. This is a preliminary finding built substantially on how deeply enterprises are locked into a small number of cloud providers, which between them account for roughly two-thirds of EU cloud revenue, according to Synergy Research Group data. We examined that ruling in detail last month.
A billing system briefly incapable of telling a customer what they owe, at one of the two firms named in that case, is not the evidence Amazon would have chosen to hand regulators. It doesn’t change the substance of the case, but it does make for an awkward footnote.
What It Means for AWS Customers
For most users, the practical answer is nothing. No invoice was affected, and no payment was taken. Amazon says no action is required. The more instructive implication is subtler. A dashboard is an articulation of something from a vendor, but not a guarantee. It’s potentially worth a moment’s scepticism before it changes anyone’s behaviour.
According to subsequent technical reporting on the incident, the first instinct at more than one company wasn’t to suspect a display bug at all, but a breach. Some teams reportedly rotated access credentials before confirming the numbers were fiction.
It follows a curious pattern from last week of an AI customer service agent that recently doubled down on its own pricing error rather than flagging any uncertainty. The bill was never going to arrive. The instinct to trust your own judgement over the screen is arguably the part to remember. It is also a key lesson in how important it is to preserve the human in the loop.
