Amazon Web Services customers across the globe received catastrophic billing notices this week after a technical fault produced invoices with astronomically inflated amounts, in some cases reaching as high as US$1.5 trillion. The error affected a broad mix of users, from students and small charities to hobbyists and businesses, according to reporting from The Guardian.
Who was hit and what happened
Reports include a UK charity that normally pays a few pence for a small app, which was briefly shown as owing US$7.8 billion, and individual users in India and the United Kingdom who were stunned to see bills in the billions and hundreds of billions of dollars. One UK historian said her routine monthly charge jumped from about £15 to roughly US$245 billion for a short period.
“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,”
Such accounts illustrate the alarm the invoices caused. One student who usually pays about US$1.28 a month reported being billed US$10.9 billion; another person saw a figure of US$256 billion. Screenshots circulated on social media showed percentage increases of usage in the hundreds of millions of percent.
Why it matters
Cloud providers like AWS host millions of services and run billing systems that aggregate usage from diverse customers. When those systems err, the immediate consequences are financial confusion, potential automated alerts to payment systems and acute stress for affected customers — from individuals to small nonprofits that lack dedicated support teams.
- Invoice spikes reached up to US$1.5 trillion.
- Victims included students, charities and independent website operators.
- Reports came from multiple countries, highlighting the global reach of the outage.
Context and next steps
While major cloud providers typically have safeguards and dispute procedures, the incident underscores the operational risk organisations face when critical infrastructure is concentrated in a few vendors. Affected customers often must contact support channels, review account activity logs and, in some cases, coordinate with banks or payment providers if automatic actions were triggered by the invoices.
For Canadian organisations that rely on AWS for development, hosting or storage, the episode is a reminder to monitor billing alerts closely, maintain clear internal usage thresholds and ensure support contacts and contingency plans are current.
| Reported anomalous bill | Typical cost |
|---|---|
| US$1.5 trillion | Less than US$2 |
| US$7.8 billion | ~£0.43 |
| US$245 billion | ~£15 |
Amazon Web Services has not been quoted in the source reports included here; coverage so far is based on customer reports and screenshots shared publicly. The scope of financial or operational fallout, and any remedial steps AWS will take for affected accounts, remain to be clarified.
