Amazon Sent Customers a 1.5 Trillion Dollar Bill, Then the Rollback Failed
2026-07-17
“The company that runs a third of the internet showed a customer an invoice for one point five trillion dollars, tried to roll the change back, and the rollback did not work either.”
Late on Thursday the sixteenth, AWS customers opened their billing dashboards and found numbers that do not exist in commerce. One estimate posted to Reddit came in around two and a half billion dollars. The Guardian went with the headline figure: one point five trillion. Others were merely looking at millions or hundreds of millions, which by Thursday's standards counted as getting off lightly. Amazon's explanation was an issue with unit pricing within the estimated billing computation subsystem, which is eleven words doing the work of the word wrong.
The part that actually matters is what happened next. Amazon rolled back the recent change that caused it, and the rollback did not resolve the issue. That is the sentence. Not the trillion, which is funny, but the rollback, which is the thing every engineer in the world reads with a cold feeling in their stomach. The wrong numbers stayed up overnight. Customers found out from their own dashboards and from each other on Reddit, not from AWS. For a provider whose entire proposition is that they handle this so you do not have to, that is a rough sequence of events.
Nobody was actually charged, and Amazon said publicly within about a day that the displayed charges do not reflect actual usage and charges. Fine. But billing is the one subsystem a cloud provider is not allowed to get wrong, because it is the only one every single customer looks at, and it is the number their finance department screenshots. And it landed on the same day the Wall Street Journal reported that Dave Brown, the senior vice president running AWS Compute, AI and Platform, was leaving for Meta. Not a connected story. Just a spectacularly bad Friday.
- Starting late Thursday 16 July 2026, AWS billing dashboards displayed wildly inflated estimated charges, with the highest reported figure at one point five trillion dollars.
- A screenshot posted to Reddit showed an estimate of roughly two and a half billion dollars, with other customers reporting figures from millions to hundreds of millions.
- Amazon attributed the fault to an issue with unit pricing within the estimated billing computation subsystem.
- Amazon's rollback of the recent change that triggered it failed to resolve the problem on the first attempt, and the incorrect figures persisted into Friday.
- Amazon spokesperson Aisha Johnson confirmed the displayed charges do not reflect actual usage and charges. Amazon has not disclosed how many customers were affected.
- 01
Nobody paid anything. No money moved, no cards were charged, and Amazon confirmed the error publicly within roughly a day rather than letting customers stew for a week. They also named the actual failing component instead of hiding behind generic incident language about elevated error rates, which is more transparency than most providers manage on a bad day. And there is a genuinely useful lesson sitting in it for everyone else: your estimated billing pipeline is a production system with real world consequences, not a cosmetic widget, and it deserves the same rollback testing as the services it is measuring.
- 01
AWS, and specifically the idea that AWS is the boring dependable one. The financial exposure was zero, so the damage is entirely reputational, and it is concentrated in exactly the wrong place: finance teams, procurement, and the people who sign renewal contracts. Every CFO who saw a nine or thirteen figure number on a dashboard now has a very concrete anecdote for the next negotiation. Customers also got burned by the communication order, learning about it from Reddit before AWS. And there is one question Amazon has notably not answered rather than denied: whether any accounts were auto suspended for apparent non payment while the fake numbers were live. Silence on that is doing a lot of work.
No meter. No surprises.
The story isn't Copilot. It's the meter. Here is the calmer way to get your code reviewed.
- Flat price for the Full Suite. No usage meter, no month-end surprise.
- Free CLI: 90 roasts a month, no account needed.
- Privacy-first: a dry-run shows the exact payload, and your secrets never leave your machine.
Works in Claude Code, Cursor and Windsurf via MCP. Open source, and proud of it.
Got something the world should see roasted? Drop it.
A full teardown from €2,99. No mercy.