On the morning of July 17, 2026, several Amazon Web Services customers reported seeing billing estimates in the millions or even billions of dollars for cloud services they had not used, with screenshots shared on Reddit showing figures as high as roughly $2.5 billion in projected monthly charges. Amazon confirmed it was investigating the issue and attributes it to a bug in its billing computation subsystem, telling affected customers the inflated estimates do not reflect actual usage or charges.
What happened
According to updates on the AWS status page, inaccurate billing data began appearing late on Thursday, July 16. A rollback of a recent change was attempted, but by Friday morning Amazon acknowledged that the rollback did not resolve the problem.
How did Amazon respond to the billing portal bug?
Amazon told affected customers that the inflated estimates do not reflect actual usage or charges. In other words, customers who were shown balances in the hundreds of millions or billions are not expected to pay those amounts.
When contacted by TechCrunch, Amazon spokesperson Aisha Johnson pointed to the status page and declined to provide further detail. Amazon also did not say whether any AWS accounts had been suspended or paused as a result of the inflated estimates.
How long is the AWS billing issue expected to last?
Amazon’s status page indicated at the time of reporting that the issue was expected to persist for several more hours.
Why does this matter for AWS customers?
Even though the billing figures were estimates rather than finalized invoices, an unexpected notification showing a billion-dollar balance is alarming for any business that relies on AWS for day-to-day operations. The incident highlights how sensitive cloud billing dashboards can be to upstream bugs, and how quickly a display error can create confusion about financial exposure. AWS customers who received unusual estimates were advised to wait for Amazon’s resolution rather than treat the figures as real obligations.
Current status
This story is developing. Amazon’s status page remains the authoritative source for updates on the billing portal bug and the expected time to resolution.
FAQ
What caused the AWS billing portal bug?
Amazon attributes the inaccurate billing estimates to a bug in its billing computation subsystem. A rollback of a recent change was attempted on July 17, 2026, but Amazon acknowledged the rollback did not resolve the problem.
Do customers have to pay the inflated AWS charges?
No. Amazon told affected customers that the inflated estimates do not reflect actual usage or charges, and customers shown balances in the hundreds of millions or billions are not expected to pay those amounts.
When did the AWS billing display issue start?
According to the AWS status page, inaccurate billing data began appearing late on Thursday, July 16, 2026, and was still under investigation on the morning of Friday, July 17, with an expected resolution time of several more hours.
This article summarizes reporting from techcrunch.com, techcrunch.com. See our editorial disclaimer for how our articles are produced.
Related coverage
Run a free scan to see your AI Visibility Score, SEO rating, and local citation accuracy.