• 2 min read
AWS billing glitch showed trillion-dollar charges
AWS customers saw billing estimates in the billions and trillions after a pricing bug on July 17, 2026. Amazon says no action is needed and fixes are still rolling out.
Image: TechRadar
AWS customers were hit with a nasty shock on Friday, July 17, 2026, when the company’s billing system began showing estimated charges in the billions, trillions, and even quadrillions of dollars.
The issue appeared in the Billing and Cost Management console, where customers check usage and costs. According to the report, AWS does not mail out invoices, so users discovered the problem when they logged in or received alerts. The reaction ranged from disbelief to panic.
One widely shared post came from Bharath_uwu on X, who wrote:
“I just saw $1.5 trillion on my AWS bill and my soul left my body.”
The Guardian also spotted multiple social posts tied to the glitch. Dan Harvey, head of marketing at Learning Through Landscapes, told the paper:
“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.”
Not everyone responded the same way. Some users joked about the mistake, including Chinmay on X, who asked others to share their biggest AWS bills and said his had reached $333B. Others were less amused. Mr Doob wrote on X that someone could have had “a real heart attack.”
Recommended reading
Japan’s data center boom hits urban backlash
AWS began posting status updates at around 1:30AM PDT on Friday, saying it was investigating “inaccurate estimated billing data” in Cost Explorer. Later, the company said it had found the cause:
“We have identified the root cause as an issue with unit pricing within the estimated billing computation subsystem, and we are working on a mitigation.”
Hours after that, AWS said corrected cost and usage data was still being backfilled and that progress was “slower than anticipated.”
The key point: customers are not being asked to pay these bogus amounts. The problem affected billing estimates, not the underlying cloud platform. The report says there were no outages or performance issues tied to the incident.
AWS even tried to joke about the failure on X, calling it a “Typo alert” and saying no customer action was needed.
Enterprise Editor
Marcus follows the money. He covers enterprise software, cloud architecture, and the tectonic shifts in Big Tech strategy. He translates dense earnings calls and complex M&A activity into actionable insights about where the industry is actually heading. If a tech giant makes a silent pivot, Marcus is usually the first to notice.
via TechRadar
