AWS: Inaccurate Estimated Billing Data - $1.7 BILLION

AWS: Inaccurate Estimated Billing Data - $1.7 BILLION8 points by nprateem 42 minutes ago | hide | past | favorite | 11 commentsURL already posted: https://health.aws.amazon.com/health/statusI'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_skyrocketed_from_around_5_cents_per/ help

Apparently what used to be `GB of storage consumed` is confused with `Bytes of storage consumed`, leading to a cool off by 2*30 error.> 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! Probably the closest I've ever been to getting a heart attack. Normally <$1 per month, and now suddenly $284,006,266,443.74. Whatever the bug is on their end, this is unforgivable. Same - just had some malicious bots running through my platform last week and really thought they found a security hole after all. Even though the amount sounded ridicoulus, I got quite nervous and a very bad feeling when I logged-in AWS and saw that price. I got estimated costs of $56.something billions. Usually ~$100/month. My heart rate currently still sits at around 160 bpm. Motherfuckers.