I’ve got an estimated bill for $1.7 BILLION over this month. Normal usage is 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!
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
It’s been 2 hours and I still haven’t fully calmed down.
reply
reply
reply
reply
reply
Host your own people. Host your own.
reply
reply
reply
reply
Folks can track it directly on AWS Health: https://health.aws.amazon.com/health/status
reply
reply
But with AWS costs rising anyway (not by that much but OK), I’m probably not the only one to start reconsidering their cloud strategy. I think this might have just pushed me over the edge.
reply
reply
“Operational issue – AWS Billing Console (Global)
Service – AWS Billing Console Severity Impacted – Inaccurate Estimated Billing Data”
reply
reply
reply
reply
reply
reply
reply
reply
reply
Insane
reply
reply
reply
reply
$103,515,940,301.79
reply
reply
reply
reply
reply
reply
Incidentaly, smaller competitors solved this issue decades ago, while the big cloud decided it is more convenient never to implement it.
reply
“Limits except for Storage” seems even easier – I don’t think I’ve ever heard of a storage-based billing story, although I’m sure one or two exist
reply
reply
reply
reply
reply
reply
reply
reply
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?
reply
reply
reply
reply
https://health.aws.amazon.com/health/status
reply
reply
reply
reply
reply
reply
reply
reply
reply
I understand people complaining about large bills, but this is over the top!
reply
reply
reply
reply
reply
reply
reply
reply
The crypto network you hosted should pay for itself in 10-20 years just like LLMs. Don’t worry. Consider Bank of America until then if you are good on credit score.
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
Phew.
reply
Looks like this is a bug w/ S3
reply
reply
All hail the new generations of our uberployers.
reply
I might be a winner.
reply
Yeah, this most certainly is bad code wrapping around a value. AWS will post a notice soon if they haven’t already.
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
Like “I was scared for a couple minutes on a Friday morning until I saw the vendor status page” is orders of magnitude away from the bar here.
reply
reply
I’m not currently running anything and have no plans to at the moment. I’ve always had a mild dread that I’ll suddenly get a bill for more than $0.00.If AWS can goof in a way that causes obviously massive bills (like today), what’s to say they can’t goof in more subtle ways and start charging small additional amounts that many people may not notice and just pay it.
If AWS can goof in a way that causes obviously massive bills (like today), what’s to say they can’t goof in more subtle ways and start charging small additional amounts that many people may not notice and just pay it.
reply
reply
reply
reply
reply
reply
$1,299,988,247,332.56!That was a fun set of emails to wake up to, figured they had to be phishing for how outrageous of a number it was. But nope! Fun little incident they’ve got going over there.
That was a fun set of emails to wake up to, figured they had to be phishing for how outrageous of a number it was. But nope! Fun little incident they’ve got going over there.
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
reply
Honestly, I would worry more about estimated billing that seems plausible in general, but is way to high for you personally.
These ridiculous amounts? Not so much.
reply
reply
reply
