AWS Billing Error: $1.7 Billion Discrepancy
Executive Summary:
- AWS is dealing with a $1.7 billion billing discrepancy.
- The issue is caused by unit errors in the billing system.
- Customers have reported receiving incorrectly high bills.
The Internet’s Verdict: 80% Concerned, 20% Skeptical
What’s Happening
AWS customers have been reporting errors in their estimated billing data, with some receiving bills that are significantly higher than expected.
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.
Causes and Consequences
The issue is caused by a mistake in the unit type in the pricing plan, which leads to incorrect metering data conversion.
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.
Some customers have reported that the issue has been ongoing for years, with one customer receiving a $7,000 refund after 14 months.
Conclusion
AWS needs to address this issue promptly to avoid further discrepancies and damage to its reputation.
Focus Keyword: AWS Billing
