Your Friday morning started with bad news. A cloud bill arrived. Not $500. Not $10k.
Billions of dollars.
For AWS customers staring at their dashboards on Friday, the numbers were impossible. Some saw estimates for cloud services they hadn’t even turned on. Amazon confirmed the glitch is real. Their billing portal is showing fake debts ranging from millions to billions.
How a billing computation bug triggered false charges
The trouble started late Thursday. Amazon noticed inaccurate billing data. They tried a fix. Specifically, a rollback of a recent change to the AWS billing computation subsystem. It didn’t work.
By Friday morning, the panic had spread. Screenshots flooded Reddit. One user claimed a charge of nearly $2.5 billion. Others showed tabs for hundreds of millions.
Why does this matter? Because panic costs time. IT ops teams scrambled to check usage logs. They verified they weren’t running data centers for other countries. They were just running normal workloads.
The numbers on the screen are wrong.
The billing estimates do not reflect actual usage and charges. — Amazon Status Page
If you’re one of these users, take a breath. You likely won’t pay the fake tab. Amazon says these figures are estimates based on bad data.
Where to check your AWS status right now
Are your services running? Probably. Amazon wouldn’t confirm if accounts were suspended or paused when pressed by TechCrunch. Spokesperson Aisha Johnson pointed to the status page and declined further comment.
That’s standard corporate deflection. But the silence speaks to the urgency. This isn’t a minor UI tweak. It’s a fundamental error in how money is calculated.
The estimated duration for this issue is “several more hours.” So what happens when it resolves?
- Data Reset: The backend numbers should align with real usage.
- Bill Correction: Invoices should update automatically.
- Account Review: Check for any throttled services during the window.
There are no refunds needed if you weren’t charged. The “debt” exists only in a broken frontend or intermediate database. It hasn’t hit the credit card terminal yet. Or at least, that’s what the statement implies.
Why did this happen? We don’t know yet. Was it a code deployment error? A database schema migration gone wrong? Amazon keeps the details close to the vest. They mentioned the “recent change” failed.
We’re all used to software breaking. Code is brittle. But making it look like you owe a small country’s GDP for a weekend’s worth of Lambda functions? That’s a specific kind of terrifying.
The clock is still ticking on the repair estimate. Sit tight. Watch your console.
