On July 17, the world of cloud technology faced an unprecedented anomaly. Clients of Amazon Web Services (AWS) received emails with preliminary bills containing figures that caused genuine shock. Instead of usual expenses, users saw numbers amounting to billions and even trillions of dollars.

"I just saw a figure of $1.5 trillion in my AWS bill, and I was absolutely terrified," one of the affected users shared with The Guardian journalists. Similar messages flooded in from clients worldwide, for whom such figures meant not just an error, but potential financial ruin.

Admission of error and attempt to fix

Amazon reacted quickly to the surge of panic, confirming critical errors in the AWS billing system. The company admitted that due to the glitch, some clients appeared to "owe" unimaginable sums for cloud services rendered.

According to official data, incorrect data began appearing in client systems as early as Thursday evening. However, the attempt to quickly resolve the issue was unsuccessful. By Friday morning, Amazon was forced to admit that "reverting a recent change did not solve the problem," and glitches continued to generate fake bills.

Data restoration and assurances

The situation began to stabilize on Friday evening. At 22:56 Moscow time, the company reported that specialists had identified the root cause of the glitch and eliminated the main problem causing incorrect data to be displayed.

Amazon also announced the start of a procedure to correct cost information for all affected clients. As promised by service representatives, the full restoration of correct data was expected to be completed by 10:00 MSK on July 19.

"The displayed calculated amounts do not reflect actual usage and charges," Amazon assured clients, trying to calm the nerves of businesses dependent on their infrastructure.

Series of incidents

This billing incident occurred against a backdrop of instability in the cloud platform's operation. Resource TNW noted that the glitch with trillion-dollar bills happened just one day after a major AWS CloudFront outage. At that time, users worldwide saw errors instead of websites, which already sparked a wave of dissatisfaction and prompted questions about the reliability of the cloud computing giant.