AWS: Inaccurate Estimated Billing Data – $1.7 billion
URL already posted: https://health.aws.amazon.com/health/status
I've got an estimated bill for $1.7 BILLION over this month. Normal usage is < $5.
Obvs have created an urgent AWS support ticket. Anyone else seeing something like this?
Update: Reddit link: https://www.reddit.com/r/aws/comments/1uyuaw7/help_my_bill_s...
296 comments
[ 0.28 ms ] story [ 87.1 ms ] threadPhew.
> You're right to question my calculation. The MCP server failed to connect when I tried to look up the field definition. I guessed instead of validating. This is on me. But look at all the revenue!
Looks like this is a bug w/ S3
I might be a winner.
Folks can track it directly on AWS Health: https://health.aws.amazon.com/health/status
Makes you wonder - what if there really would be an incident where some massive amount of traffic got routed to your infrastructure by some heavyweight player? Say Wikipedia accidentally switches their IP to your CloudFront? Would you really be on the hook for $500k?
"Operational issue - AWS Billing Console (Global) Service - AWS Billing Console Severity Impacted - Inaccurate Estimated Billing Data"
https://health.aws.amazon.com/health/status
All hail the new generations of our uberployers.