AWS Cost Explorer inflated billing estimates corrected

Sources: AWS Support status update, The Register, HN discussion
Summary: The AWS Cost Explorer and Billing Console incident that began 2026-07-16 at 19:38 PDT continued into 2026-07-17, with near-idle accounts shown estimated charges from hundreds of thousands to trillions of dollars and budget alerts firing on the bad figures. AWS attributed the root cause to a unit-pricing defect in the estimated-billing computation subsystem and stated the estimates do not reflect actual usage or charges. AWS began backfilling corrected figures in the Cost Management Console and said all accounts should show accurate amounts by 2026-07-18 around noon Pacific. No evidence indicates invoices or payment processing were affected.
Why it matters: Automated budget alerts and anomaly detection fired on fabricated numbers, so teams wired to page or throttle on cost signals had to separate a display defect from a real spend event.
Follow-up: Watch for a published root-cause writeup and confirmation that budget-alert and anomaly-detection false positives clear without customer action.