AWS Billing Error: $1.7 Billion Discrepancy
Executive Summary:
- AWS is facing a $1.7 billion billing error due to unit discrepancies.
- The error is caused by incorrect unit types in pricing plans.
- Customers have reported receiving excessively high bills, with some reaching millions of dollars.
The Internet’s Verdict: 80% Concerned, 20% Amused
What’s Happening
AWS customers have been reporting inaccurate estimated billing data, resulting in some cases with bills reaching millions of dollars.
Forum Voices
Customers have taken to forums to share their experiences and offer explanations for the error.
Ive dealt with this error at AWS. It’s a unit error. In my case we _meant_ to charge like 5¢/GB, but missed the unit (GB), and then the billing system defaults to bytes. 5¢ per Byte of data transferred meant some customers were seeing MM bills within hours.
Another customer reported receiving an email warning of a budget threshold breach, only to find their actual cost was $78 million.
I got 3 consecutive emails warning that my budget crossed its $18 threshold. Opened it up: cost was 78 million. Thought it was a phishing attempt, logged into my actual account, and… still 78 million. EMOTIONAL DAMAGE.
Conclusion
AWS is working to resolve the issue, but the error has left many customers concerned about the accuracy of their bills.
Focus Keyword: AWS Billing