What an `effin disaster. The alert almost gave me a heart attack.
AWS: Inaccurate Estimated Billing Data – $1.7 billion
351–360 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#352Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#353Earlier quoted context omitted.
I saw this in action on a smaller scale. In a past job, my wife organized events for a decent sized company. After an event, she'd typically have a $300k+ balance on her corporate Amex. When she went on maternity leave, the person filling in for her job neglected to actually pay the bills, so when she returned there were quite a few emails and voicemails from Amex regarding the over $500k balance. The messages starte…
I think that this might reflect more on Amex to be honest. Amex realises that threatening would hurt their business trust more than anything. During the great depression, Amex accepted checks from other banks which were falling and paying through their own wallet as a matter of integrity. Amex has always been built around this idea of trust and prestige. They make most of money from what I have heard on the transacti…
Interesting. And hard to square with my perception of banks as completely mercenary and ruthless. I had a decade-long personal boycott (I know, LOL) of Amex after they, because, with otherwise perfect credit, I forgot about a $30 department-store card bill and got a 30-day-late mark on my report, Amex got spooked and abruptly closed both my never-late accounts with them (which were at or close to 0 balances). This was around 2008 though, so perhaps this was a genius algorithm designed to try and detect the very first whiff of consumer defaults, so they assumed that $30 was the first domino to fall of my personal financial ruin that could lead to me charging my accounts to the max and then going bankrupt.
(I eventually admitted to myself that Amex isn't a person and thus not really capable of insulting my honor, but it took a while!)
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#354One can almost smell the vibes. This is peanuts compared to a major cybersecurity catastrophe that’s surely in the making. To give credit to the technology and the people using it - and I’m not being facetious - it’s actually incredible that at the current levels of usage the unprecedented catastrophic event has not yet happened.
Always messing up some mundane detail!
$1.7-billion isn't a mundane detail Michael!
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#355I 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.
Enterprise account . We got - 3trillion and change
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#356[deleted]
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#357I realized recently that Whole Foods no longer automatically and reliably detects your Chase Amazon Prime credit card when paying. So they don’t give you the discounted pricing automatically. I wonder how many customers are checking out the way they always do and are paying full price when, for years and decades, this worked fine. The customer service people I talked to in the grocery store said this changed sometime…
There are a hundred small things like this that seem to be popping up in what used to be simple and reliable systems and as much as I know they aren’t ALL because of vibe coding I can’t help but wonder how much is.
Weirder is what happened a day later. I got an email that said my Chase Amazon Prime credit card was being re-associated with my Amazon.com account.
I never reported this nor took it up with either Amazon or Chase directly. There was a refund of my Whole Foods purchase (they needed to void my purchase and re-ring everything to give me the discounts.. I asked them to refund my purchase and I’d do without my Whole Foods purchase entirely).
Looking back I think at least 3 recent visits were charged to me at full price because of all this. Hard not to think of enshittification and whether Amazon Prime is even worth it, alas.. I live in a fairly rural area at the moment and need delivery.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#358https://health.aws.amazon.com/health/status "Operational issue - AWS Billing Console (Global) Service - AWS Billing Console Severity Impacted - Inaccurate Estimated Billing Data"
Update as of 7:53am PDT:
"The rollback of a recent change did not resolve the issue and we are continuing to investigate multiple mitigation paths. Estimated bill updates remain paused."
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#359Current month $13,648,114,178,401.01 188,253,226,212% Forecasted month end $18,729,381,032,152.4 Apparently my company owes the combined GDP of France, Germany, and UK to AWs.
"Have you considered using Reserved Instances? You could save up to 2 trillion dollars next month. Book a call with your AWS rep."
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#360If AWS was a predatory mobile gacha game, we'd get 300 apology gems as credit to our accounts for this mixup, to help us in our rolls for the next 3-letter acronym they release.
Do the right thing for the players, Matt!