AWS Billing Console Loses the Plot, Tells Users They Owe Trillions

If you received an AWS billing alert this morning suggesting your cloud spend had somehow ballooned into the billions, breathe. You have not accidentally trained a frontier model on someone else's dime.

Amazon Web Services confirmed a fault in its Billing Console on Friday that caused Cost Explorer to spit out wildly inaccurate estimated charges to customers. The issue surfaced on the AWS Health Dashboard just after 1:30am Pacific time, with Amazon describing the culprit as "an issue with unit pricing within the estimated billing computation subsystem." Which is a careful way of saying someone broke the maths.

Within about ninety minutes of investigating, AWS claimed to have identified the root cause. As a short-term fix, they paused further updates to billing estimates, meaning customers were stuck looking at absurd figures but at least those figures stopped getting worse. Amazon was clear that no actual charges were affected. This was purely an estimation problem, not a billing one.

How bad did the numbers get? Spectacularly bad. Reddit and Hacker News filled up fast with screenshots and disbelief. One user whose genuine monthly bill came to nineteen cents was greeted with an estimated charge of nearly two and a half billion dollars. Others reported estimates ranging from a comparatively modest $126,000 to a frankly cosmic $2.5 trillion. The kind of numbers that make you briefly wonder whether you left a GPU cluster running by accident.

Amazon has since updated its status page to confirm the underlying issue has been mitigated and that corrected billing figures will be backfilled across accounts, with everyone expected to see accurate numbers by noon Pacific time on Saturday, July 18th.

AWS declined to give any further technical detail beyond what appeared on the dashboard. For now, the advice is simple: ignore the number, do not raise a ticket, and maybe avoid showing your finance team the billing console until Saturday.