AWS billing system bug sparks panic with fake billion-dollar invoices
That’ll be $495 billion, please
AWS bill. By Cybernews.
- AWS customers saw fake bills reaching billions and even trillions of dollars after a billing console bug.
- Amazon paused billing estimates, identified the issue, and said AWS services were operating normally by July 18.
- Customers reported panic on social media, with one invoice showing nearly $495 billion versus $1.63 the previous month.
- The incident matters because businesses may have disabled critical services, risking downtime and lost revenue.
Key Takeaways by nexos.ai, reviewed by Cybernews staff.
Some people had the scare of their lives after receiving Amazon’s latest invoice. An undisclosed number of customers were billed absurdly high amounts, with some reaching up to a trillion dollars.
On Friday, July 17th, Amazon noticed issues in its AWS Billing and Cost Management Console that caused some clients to receive “inflated estimates,” ranging from several hundred thousand dollars to billions of dollars.
To prevent further inaccurate billing estimates from being displayed, Amazon temporarily paused its billing systems.
After a few hours, Amazon’s engineering teams identified the root cause within the Console’s billing computation subsystem. However, identifying the issue and solving it are two completely different things.
Several AWS customers took it upon themselves to voice their concerns.
A user expressed his frustration on X, stating that due to the platform’s character limitation, he added a screenshot to show people he had been billed almost $495 billion. For comparison, in June, he was billed only $1.63.
Another user complained that he almost had a heart attack, and another one said that his “soul had left his body” when he received an invoice of approximately $1.5 trillion.
“Yeah, shit myself when I saw my old dormant personal AWS send me an alert for $26,538,759.36,” one user wrote on Reddit.
Stay updated with our latest stories and follow us on social media
Be the first to discover new stories, ideas, and updates from our team.
It took Amazon multiple attempts and several more hours to fix the issue. Eventually, on July 18th, the Billing and Cost Management Console worked properly again.
“We apologize for the alarm this incident caused our customers and are conducting a thorough retrospective to prevent events like this from reoccurring, as well as improve our response when billing incidents occur. The issue has been resolved, and all AWS services are now operating normally,” Amazon said on its AWS Health Dashboard.
In hindsight, affected users will most likely laugh at what happened because the billing amounts were absolutely absurd. On the other hand, it’s likely that some organizations immediately disabled important services as a precaution, which could have led to lost revenue and downtime.
As reported by TechCrunch, an Amazon spokesperson refused to answer questions about the bug and wouldn’t say if any AWS accounts had been suspended or paused as a result of the issue.
