On July 17, 2026, people who use Amazon Web Services (AWS) — Amazon's cloud computing platform — logged into their accounts to find bills reaching as high as $1.5 trillion. A glitch in the system had produced wildly inflated charges. The Guardian reported the story.

The wrong figures started showing up at 3:38am UK time on Friday, July 17. AWS said the problem was "an issue with unit pricing within the estimated billing computation subsystem," according to The Guardian. After about an hour and a half of investigation, AWS turned off the bill estimation system entirely. The company said it expected "full resolution to take multiple hours as we work through recomputing the estimated billing data," in a statement also posted on its health status page.

The scale of the miscalculation varied, but every case was far beyond what customers actually owed. Bharath, an AWS customer who posted on X, saw his bill reach $1.5 trillion, with the console reporting usage up 745,728,201,771% over the previous month. Dan Harvey, head of marketing at the UK charity Learning Through Landscapes, received a $7.8 billion bill for an app that normally costs less than a pound per month. Andrea Zuvich, a historian in Bolsover, Derbyshire who runs The Seventeenth Century Lady website, was billed $245 billion against her usual $15 monthly charge. Sachin, a student in Delhi whose typical monthly bill runs $1.28, saw a figure of $10.9 billion. Another unnamed customer reported being billed $256 billion.

AWS apologised "for any confusion and concern around these costs."

The Guardian reported that Amazon had been approached for comment at the time of publication.

AWS has two kinds of billing. One is the final bill — the real amount a customer owes. The other is an estimate, a rough projection that updates in real time as customers use the service. Think of it like a petrol gauge in a car: it gives you a sense of how much fuel you're using before the final bill arrives. What broke was the estimation part. When a component that calculates unit prices failed, it sent inflated numbers into every customer's account dashboard.

That AWS engineers took about ninety minutes to find and shut down the estimation system, rather than fixing it instantly, shows how hard it is to isolate a single broken part inside a system that processes usage data across the entire world.

A few things matter for people who manage AWS accounts or budgets. First, the glitch only affected the estimated figures shown on screen — not the final amounts customers were actually charged. Nobody was billed a trillion dollars. But the estimation system is what organisations use to watch their costs in real time, set budget alerts, and track spending. If those estimated numbers feed into automated systems or third-party tools that manage cloud costs, the wrong figures could cause a lot of disruption even though no money actually moved. Second, AWS said it would take "multiple hours" to fix the estimates, meaning customers could not see accurate cost information for a meaningful part of the business day.

The affected customers tell a story of their own: a student in Delhi, a small charity in the UK, an independent historian running a niche website. For these smaller customers, a billing shock of this size is not a minor curiosity but a genuine scare, especially if a credit card or credit limit is linked to the account. The fact that no large companies appear in the reported cases may simply reflect who is most likely to post online about a billing surprise — not who was actually affected.

The bigger picture here is about trust. Estimated billing is a monitoring tool, and when that tool produces numbers that are not just a little wrong but off by billions of dollars, it raises questions about how much customers can rely on it. AWS's billing dashboard is, for many organisations, the only place they can check their cloud spending between monthly invoices. This incident shows that the estimation system can break badly and all at once, and that fixing it takes hours, not minutes.