AWS Billing Console Bug: Inaccurate Estimated Billing Data Incident

AWS Billing Console Outage Causes Massive Overestimations

An operational issue with the AWS Billing Console (Global) service resulted in inaccurate estimated billing data being displayed to users. This bug caused the system to project monthly costs that were exponentially higher than actual spending, leading many users to receive alerts for bills ranging from millions to trillions of dollars.

User Impact and Reported Figures

Users reported a wide variety of extreme overestimations. While some users typically spend only a few dollars per month, their projected bills spiked to astronomical levels:

• Billions of Dollars: Multiple users reported projections of $140 billion, $400 billion, and $4 billion.
• Trillions of Dollars: One user reported a projected cost of approximately $1.3 trillion, while another claimed an estimate of $10 trillion.
• Millions of Dollars: Some users saw projections as low as $28 million, despite having minimal actual spend.

AWS Official Status and Response

AWS acknowledged the issue through the AWS Health Dashboard. The incident was categorized as an "Operational issue - AWS Billing Console (Global) Service," with the severity marked as "Impacted," and the status specifically citing "Inaccurate Estimated Billing Data."

Community Observations and Technical Speculations

Users on Hacker News discussed the potential technical causes of the bug. Several contributors speculated that the bug was a result of a resulting in a rounding error or a buffer overflow, with one user noting:

"Due to a rounding error" or a buffer overflow, you now owe INT_MAX to BaldGuyCloudService. Yeah, this most certainly is bad code wrapping around a value.

Other users pointed out the absurdity of the absurdity of the figures the figures are comparable to national GDPs or total AWS revenue, noting that figures like $117 billion were comparable to the GDP of Kuwait.

Support and Resolution

Users reported difficulty in finding the issue on the AWS dashboard. Some noted that the critical information was hidden away on the support page rather than being prominently displayed on the main billing dashboard, leading to initial panic before the official "operational issue" message was located.