AWS customers worldwide were startled after the AWS Billing and Cost Management Console and Cost Explorer began displaying extraordinarily high projected cloud costs.
Some organizations reported estimated monthly bills reaching trillions of dollars, triggering budget alerts and prompting concerns over potential unauthorized AWS usage.
AWS confirmed the issue through its Health Dashboard and AWS Support account on X, stressing that the inaccurate figures are limited to estimated billing data. The company said actual charges and verified usage records remain unaffected.
The issue began at approximately 7:38 PM PDT on July 16, according to AWS. Initial updates said engineering teams were investigating why Cost Explorer was reflecting inaccurate estimated billing information.
In an update published at 3:03 AM PDT on July 17, AWS said it had identified the root cause: a problem involving unit pricing in its estimated billing computation subsystem.
“AWS has identified the root cause as an issue with unit pricing within the estimated billing computation subsystem,” the company said. “The displayed billing estimates do not reflect actual usage and charges.”
AWS Cost Explorer is a cloud cost-management tool that helps customers visualize historical usage, forecast spending, and identify cost trends. It relies on estimated pricing calculations during a billing period, while final invoices are based on validated metered service usage.
The outage appears to have affected the estimate-generation layer rather than AWS’s underlying usage metering or invoicing systems. In practical terms, an incorrect unit-price value could multiply legitimate usage figures into implausibly large projected charges.
AWS said it is working on a mitigation and warned that full recovery will take multiple hours after the immediate issue is addressed. This is because the company must recompute estimated billing data across affected customer accounts.
AWS also said no customer action is required at this time.
The AWS Support update triggered widespread reactions on X, where customers shared screenshots of unexpected cost projections and budget alerts. Several users described receiving alarming notifications that suggested their organizations were suddenly facing massive cloud bills.
Others pointed out that the projected amounts were clearly impossible, with estimates exceeding the annual revenue or market value of many major companies.
he event also renewed discussion about the operational impact of automated AWS Budgets alerts, which can quickly escalate billing anomalies to finance, engineering, and security teams.
While the estimates were erroneous, users should still treat unexpected AWS billing alerts seriously. Cost spikes can also result from compromised credentials, exposed access keys, cryptomining activity, misconfigured autoscaling, or an accidentally deployed resource-intensive workload.
AWS customers do not need to alter resources or make payments in response to the incorrect estimates. However, teams should continue monitoring their accounts and independently validate usage through service-level dashboards, CloudTrail activity, AWS Config, and Cost and Usage Reports.
Security and FinOps teams should also confirm that anomalous alerts disappear after AWS completes the recalculation process. If a cost increase persists after the AWS incident is resolved, customers should investigate for unauthorized activity or configuration changes.
AWS has not provided a final resolution timeline but said it would issue further updates as mitigation progresses.
Strengthen Your SOC by Accelerating Threat Detection & Rapid Investigations. -> Integrate ANY.RUN With Your SOC Now.
