Some AWS customers opened Cost Explorer or the billing console on Friday and saw estimates in the millions or billions of dollars, TechCrunch reported. Amazon confirmed a bug in its billing computation subsystem. The company says the figures do not reflect actual usage or charges.
AWS status posts said the bad data started late Thursday. A rollback of a recent change had not cleared the problem by Friday morning. Reddit screenshots showed quotes from a few million dollars up to about $2.5 billion for a single month. Finance channels filled with screenshots, panic, and support tickets.
Even when a bill is fake, the side effects are real. Budget alarms fire. Automated policies can throttle accounts. CFOs forward emails with all-caps subject lines. On-call engineers waste hours proving nobody spun up a secret mining fleet.
Until corrected numbers land, treat impossible totals as display errors. Screenshot the console. Open a support case. Check whether any cost-anomaly automation already acted on the bad data. Partners who bill clients need the same language ready, including ticket IDs.
Cloud billing systems span thousands of SKUs, tax rules, reserved capacity, and committed spend. A computation bug in that stack is rare in public view. That is why the screenshots traveled so far. The useful habit remains boring: reconcile estimates against usage metrics you control.
If you run FinOps, document which alarms fired and which did not. Add hard ceilings so auto-remediation cannot shut off production over a display glitch. Check invoice export jobs that might have cached the bad figures. Intermediate systems that treat Cost Explorer as gospel can write nonsense into finance records.
Amazon will likely publish a clearer postmortem once the subsystem is stable. Until then, assume console estimates can fail independently of actual charges. That is cold comfort for a CFO staring at a nine-digit number. It is still the operational truth of this outage.
Keep a human in the loop before acting on overnight jumps of several orders of magnitude. Reconcile Cost Explorer against CloudWatch counters, pipeline logs, and your own request meters. That boring checklist beats panic tear-downs every time.
Share Amazon's confirmation early with finance partners. Avoid promising invoice credits before AWS clarifies what actually posted. Most of these figures should never reach an invoice. The danger is intermediate systems that treat the console as gospel.
This incident will feed multi-cloud and cost-observability conversations for a while. The durable lesson is simpler. Treat console estimates as a signal, not a command, until they match independent meters you trust.