AWS Goes Haywire: Customers Panic After Receiving Bills in the Trillions

An internal error in the billing systems of Amazon Web Services (AWS) has caused customers to see completely outrageous amounts on their dashboards in recent days. In several cases, companies and developers received notifications indicating estimated costs of billions or even trillions of dollars, despite normally having monthly expenses of just a few cents or tens of dollars.

Among the most significant incidents was that of Bill Radjewski, manager of the CollegeFootballData.com project, who received a notice regarding usage costs of 1.5 trillion dollars. The account, which had never exceeded two cents in monthly spending over the previous six years and usually recorded charges of just one cent, also displayed an even higher billing forecast for the next cycle.

Reports began to multiply rapidly starting on July 17, involving customers from various geographical areas, particularly the United States and Europe. Among the reported cases was a bill of 7.8 trillion dollars received by a British company that had spent just 43 cents the previous month, a student in Delhi who went from 1.28 dollars to 10.9 billion dollars, and another user who saw a request for 1.5 trillion dollars, with a percentage increase of over 745 billion compared to the previous month.

The company, of course, was immediately contacted by the affected parties and confirmed the existence of the issue, clarifying that no actual charges were made. AWS identified the cause as an anomaly in the subsystem responsible for calculating billing estimates, related to the unit prices used during cost processing. Subsequently, the group announced the rollback of a recent change to the calculation system and the restoration of the last working configuration, temporarily suspending the cost estimation service. The process of reconstructing the correct data, according to the company, took longer than expected.

According to information provided by AWS, the malfunction affected several cloud platform services, including EC2, S3, and network services, as well as monitoring tools like Cost Explorer and daily consumption reports. In many cases, spending graphs showed sudden vertical increases even in the absence of operational activity, while automatic budget control systems sent notifications of exceeding set thresholds. Amazon also publicly commented on the incident with a message posted on social media, calling the episode a "small oversight" and reassuring users that no action was needed as technicians completed the restoration of the correct data.