AWS: Inaccurate Estimated Billing Data – $1.7 billion
Points and comments are a snapshot, not live.
AWS billing system displayed erroneous estimated bills up to $241 billion for users.
Multiple AWS users reported estimated bills ranging from $34 million to $241 billion, despite normal usage under $5 per month. The bug, linked to an AWS health status update, appears to have confused gigabytes with bytes in S3 billing calculations. Users received panic-inducing alerts and many tore down infrastructure in response. The billing display system is separate from the actual payment processing system. AWS support tickets were created, with users awaiting resolution.
The error caused real distress: one user reported nearly having a heart attack, another physically vomited from shock. Some users nuked their entire setups before realizing the error. The thread includes speculation that the bug resulted from AI-generated code ("vibe coding") with inadequate testing.
What commenters are saying
Dominant sentiment: widespread panic and anger. Users reported estimated bills between $34M and $241B, with many sharing visceral reactions (heart palpitations, vomiting). Commenters criticized AWS for multiple failures: no automated kill switch for anomalous billing spikes, lack of regression testing, and potential AI-generated code ("vibe coding"). There is speculation the bug conflated bytes with gigabytes (a 2^30 error).
Two camps emerged: those who immediately nuked their infrastructure in panic, and those who recognized the absurdity but still spent hours auditing. One commenter noted the irony that laughably wrong errors are preferable to subtly wrong ones that might go unnoticed. The thread includes a request for a law requiring companies to pay compensation equal to erroneous amounts.