Billing software error sends billion-dollar AWS estimates
AWS suffered a billing system glitch on 17 July 2026 that caused its Cost Explorer tool to display wildly inflated estimated bills, with some customers seeing figures in the billions or even trillions of dollars. Amazon said the errors were confined to displayed estimates rather than actual charges, and urged affected customers not to panic while it investigated and fixed the underlying fault.
The issue, first flagged on the AWS Health Dashboard at 1:33am Pacific time, was traced within about 90 minutes to a fault in "unit pricing within the estimated billing computation subsystem." AWS paused further updates to the inflated figures, then said it had identified and mitigated the root cause, with corrected numbers expected to be backfilled by noon Pacific on Saturday 18 July. Users on Reddit and Hacker News reported extreme examples, including one customer whose usual $0.19 monthly bill was estimated at nearly $2.5 billion, with others quoted figures as high as $2.5 trillion.
In short
- AWS billing tool briefly showed estimates in the billions, even trillions
- Amazon said actual charges were unaffected, only displayed estimates
- Fix rolled out with corrected figures expected by Saturday noon Pacific
Steelman: both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
AWS's response to this display error exemplified effective incident management: rapid identification of the root cause within 90 minutes, clear communication through official channels that actual customer charges were unaffected, and a concrete timeline for restoration. Complex billing systems occasionally experience glitches, and what demonstrates competence is how quickly issues are resolved and whether critical safeguards function. AWS's transparency, speed, and the fact that protective mechanisms worked as intended represent responsible handling of a technical problem.
The case against
The scale of these billing estimate errors—reaching £2.5 trillion—indicates that fundamental validation safeguards failed to prevent obviously impossible figures from being generated and displayed. For mission-critical infrastructure, unit pricing computation should be architecturally protected against such catastrophic failures through data validation, bounds checking, and rigorous testing. The incident raises legitimate questions about whether AWS's quality assurance processes adequately match the severity of systems they protect, and customers discovered the problem through social media rather than proactive AWS notification.
Explained simply
Amazon Web Services is a platform that rents computing power and data storage to businesses and individuals worldwide. Its Cost Explorer tool helps customers estimate and track their monthly spending on these services.
On 17 July 2026, Cost Explorer began displaying wildly inflated estimates of what customers would owe. Some users saw estimated bills in the billions or even trillions of dollars, far exceeding their actual spending.
Amazon confirmed that the inflated figures were errors in displayed estimates only and that no customer was actually charged these amounts. The company traced and fixed the underlying technical fault within about 24 hours of first noticing the issue.