AWS estimation glitch hits customers with phantom $1.5tn bills
A pricing computation error in Amazon Web Services' billing system generated phantom invoices reaching $1.5 trillion, exposing operational risks in the cloud giant's automated financial infrastructure.
Amazon Web Services customers were met with erroneous invoices reaching as high as $1.5 trillion on Friday. A systemic glitch in the cloud provider's billing console generated the phantom charges for accounts that normally pay just a few dollars a month.
The Seattle-headquartered company traced the issue to its estimated billing computation subsystem. Specifically, an error in unit pricing surfaced at 3.38am UK time. AWS disabled the estimation tool after an hour and a half, stating that recomputing the accurate data would take several hours.
For corporate executives and market professionals, the incident highlights the operational risks embedded in automated financial infrastructure. While the astronomical figures represented estimated costs rather than finalized charges, the malfunction disrupted the real-time budget management dashboards used by finance teams. As the dominant global cloud provider, such technical failures at AWS ripple across a vast ecosystem of startups and multinational corporations.
The distorted metrics triggered immediate panic among users unaccustomed to such extreme variance. “I almost had a heart attack when I received an email alert from Amazon Web Services with the billing for our charity’s school grounds audit app,” said Dan Harvey, head of marketing at Learning Through Landscapes. His organization's estimated bill spiked from 43 cents the previous month to $7.8bn.
Individual users faced similarly alarming outputs. A Delhi student named Sachin, whose typical monthly bill is $1.28, was presented with a $10.9bn charge. “Could you please investigate,” he asked AWS support.
Historian Andrea Zuvich saw her website's usual $15 monthly estimate balloon to $245bn. “You can imagine we were pretty surprised,” she said. Another unnamed customer, facing a $256bn liability, simply asked: “How did this happen?”
The scale of the miscalculation turned the system failure into a viral moment on social media. “I just saw $1.5tn on my AWS bill and my soul left my body,” posted a user named Bharath on X. Another user, Gerred, summarized the morning sentiment by writing: “Good morning to everyone enjoying their heart attacks.”
AWS apologised “for any confusion and concern around these costs” as engineers worked to restore normal service. “On a more serious note, this may have alarmed some people very greatly, and even have caused health issues,” Zuvich noted. The outage ultimately tested the tolerance of customers who expect absolute precision from the financial plumbing of the world's largest cloud platform.
