Some Amazon Web Services (AWS) users woke up to what would easily be one of the worst ways to wake up - a bill for more than a billion dollars. Amazon confirmed Friday its AWS billing portal fired off charges for some customers to the point of absurdity, with one AWS customer being told they owed $2.5 billion for the month.

Amazon has confirmed a system error was tracked back to a recent change to the billing computation subsystem, which Amazon said was rolled back but did not resolve the issue. Amazon emphasized that the inflated charges do not reflect actual usage, and customers affected are likely not financially responsible for the amounts. Screenshot evidence from Reddit shows a range of phantom invoices, from millions to hundreds of millions of dollars, and in some cases, such as this video, AWS customers receiving a bill for $2.2 billion of AWS usage they didn't actually use.
Popular Now: Valve confirms if Half-Life 3 will be a Steam Machine exclusiveAmazon spokesperson Aisha Johnson declined to comment further on the matter, directing all questions to the company's status page, which outlines the error and how Amazon is dealing with it. AWS is a cornerstone of modern tech operations and one of the biggest cloud infrastructure players today, which only further compounds the severity of a glitch of this scale, which may be viewed by affected customers as a reason to trust Amazon less. While the billing system is expected to stabilize in the coming hours, the damage to Amazon's reputation may linger.


Frequently Asked Questions
TweakBot answers common questions about this news using TweakTown's own coverage from this page and related content from our archive. Tap a question to reveal the answer, or type your own below.
Which AWS customers received the billion-dollar bills and how can I check if my account was affected?
Has Amazon confirmed that affected customers will not be financially responsible for the phantom charges?
How long did the billing computation error persist and is the billing portal now stable?
Could this billing glitch affect usage reports, invoices, or cost-allocation tags I rely on for accounting?
Have a question not listed here? Ask below and TweakBot will answer it.
For now, affected users are left waiting for clarity and hoping their bank accounts remain untouched, which I would assume won't happen, and in the event of it happening, Amazon would be required to compensate customers.






