AWS billing glitch shows some customers owing billions of dollars

Amazon Web Services customers woke up on July 17 to billing dashboards showing charges in the hundreds of millions, and in at least one case roughly $2.5 billion, after a malfunction in AWS's billing computation subsystem generated wildly inflated estimates, as first reported by TechCrunch. Amazon has confirmed the figures are inaccurate and does not reflect actual usage, but as of publication the company had not fully resolved the underlying issue.

What went wrong

Amazon attributed the malfunction to "a recent change" made to the billing computation subsystem, without specifying further technical detail. Engineers attempted a rollback Friday morning to reverse whatever change triggered the bug, but according to Amazon's own status page, the rollback did not resolve the issue, leaving affected customers looking at grossly incorrect bill estimates for several more hours while the company continued investigating.

Screenshots shared on Reddit and elsewhere showed a range of erroneous figures, from customers seeing estimates in the low millions up to the billion-dollar range for a single month of cloud usage — numbers that would be implausible even for AWS's largest enterprise customers. Amazon has stated clearly that no accounts were suspended or restricted as a result of the erroneous billing, and that the displayed figures do not reflect what customers actually owe.

Why a billing bug at this scale matters

AWS is the dominant cloud infrastructure provider globally, and its billing systems underpin financial planning, budgeting, and in some cases automated cost-management tooling for a huge share of internet-dependent businesses. A malfunction that generates billion-dollar phantom charges — even temporarily and even clearly mislabeled as inaccurate — creates real operational disruption: finance teams have to manually verify real spend against dashboard numbers they can no longer trust, and any automated systems that key off billing thresholds risk triggering false alerts or unintended actions.

The incident also raises a narrower but pointed question about AWS's internal safeguards. A billing computation error of this magnitude — inflating charges by orders of magnitude rather than a modest miscalculation — suggests the change that caused it bypassed whatever validation would normally catch numbers that far outside plausible ranges before they reached customer-facing dashboards.

What's still unknown

Amazon has not disclosed how many customers were affected, whether the erroneous billing subsystem also touched actual invoicing (as opposed to just dashboard estimates), or what the underlying code change was that triggered the malfunction. The company also hasn't given a firm resolution timeline beyond saying the issue was expected to persist for "several more hours" as of Friday morning. Given AWS's scale, even a narrowly scoped billing subsystem bug touches a meaningful number of businesses simply because of how many companies run infrastructure on the platform.