Rubbish Check
Guardian Business · 17 July 2026
source“Amazon Web Services customers receive bills for up to $1.5tn after global glitch”
R3/ 10
Lightly altered
Rubbish Rating — 1 = base fact, 10 = pure rubbish
12345678910
In short
Rubbish Talk rates the Guardian's claim that AWS customers "received bills" for up to $1.5tn a 3/10 because the figure and panic are real and verified, but the piece never tells readers AWS confirmed the numbers were broken estimates, not actual invoices.
The Verdict
Lightly altered. The $1.5tn figure and the customer panic are accurate and independently verified, so this is close to the base fact. It drops from a clean 1 because the article omits AWS's own clarification, reported by multiple other outlets, that the erroneous figures were display estimates that did not reflect real charges owed.
What actually happened
A bug in AWS's estimated billing computation subsystem, starting around 3:38am UK time on 17 July 2026, caused the Billing and Cost Management Console to display wildly inflated projected charges, some reaching trillions of dollars, for customers whose actual monthly usage was cents or dollars. AWS paused the estimation system and said a fix would take several hours.
Key facts
- Root cause: "an issue with unit pricing within the estimated billing computation subsystem" that AWS identified after roughly ninety minutes of investigation.
- Scale: user Bharath posted a screenshot showing usage "up 745,728,201,771% on the previous month" with a $1.5tn bill, matching the Guardian's headline figure exactly.
- Other outlets recorded even higher estimates: one Reddit user reportedly saw a projection as high as $4.2 trillion, per Engadget's reporting, and separate reports cited figures ranging into the tens of trillions.
- Critical caveat missing from the Guardian piece: AWS explicitly stated the displayed figures "do not reflect actual usage and charges," per TechCrunch's reporting on Amazon's own confirmation.
- Case cited by the Guardian: charity worker Dan Harvey's bill jumped from 43 cents to $7.8bn overnight, an anecdote independently corroborated by a crypto-focused outlet's report of the same charity.
What to watch for
- Watch whether AWS issues a formal post-incident report detailing the scope (how many accounts affected) and any compensation, since the Guardian piece stops at the apology stage.
- Watch for follow-up coverage clarifying, as several outlets already have, that Cost Explorer estimates are separate from metered invoices, since that distinction determines whether this was merely alarming or genuinely financially threatening.
- Watch the promised Saturday noon Pacific full-resolution deadline for confirmation the backfill actually completed on schedule.
About this scoreThe R-Score is Rubbish Talk's editorial opinion on how far a headline's framing sits from what the underlying facts support. It is a judgement about presentation and emphasis, not an allegation that any outlet has acted dishonestly. Every figure we rely on is linked under Receipts so you can check it yourself.
Related
