“Outages are a GOOD THING!” / FOX talking head
Comment on Load bearing Tupperware
CallMeAnAI@lemmy.world 4 weeks agoAnd? God forbid we touch grass for 6 hours a year.
tomiant@piefed.social 4 weeks ago
CallMeAnAI@lemmy.world 4 weeks ago
Sure that’s what I said.
Go ahead to rack space, or SAP, I’m sure you’ll have a much more reliable experience. Or just run your own. I’m sure it’ll be easy peasy and super reliable.
lengau@midwest.social 4 weeks ago
I touch grass every day. I want to do it on my own terms, not Amazon’s.
MajinBlayze@lemmy.world 4 weeks ago
I keep some potted grass by my desk so I can touch it whenever I want
undefined@lemmy.hogru.ch 4 weeks ago
Yeah, when I can’t access my bank account the first thing I do is “touch grass.” 🥴
CallMeAnAI@lemmy.world 4 weeks ago
Yup, I’m sure your bank would never go down on another provider. Never.
undefined@lemmy.hogru.ch 4 weeks ago
Well lucky for me they don’t use AWS so I’ve never had to find out. 🥰
CallMeAnAI@lemmy.world 4 weeks ago
balance8873@lemmy.myserv.one 4 weeks ago
Some of us have jobs. I mean I guess you have a job, but in your case losing network just means those pesky humans stop bothering you and go to a real therapist.
CallMeAnAI@lemmy.world 4 weeks ago
I’m a staff engineer who has been dealing with the results of SLAs before Amazon was an idea.
God forbid I have a p0 where I have to message a bunch of non technical directors it’s AWS not us. Much much worse than having to figure out and then pull in the team that pushed whatever untested shit made it’s way into production on a Friday afternoon.
Unless you’ve been responsible for a SaaS with SLAs in a b2b setting; I know more about the consequences of a provider outage than you.
balance8873@lemmy.myserv.one 4 weeks ago
I don’t know what you’re responding to but it doesn’t seem to be me. Either that or you forgot the username you picked for yourself in which case: whoosh
naught101@lemmy.world 4 weeks ago
Agree. That’s not related to the point I was responding to though…
AmbitiousProcess@piefed.social 4 weeks ago
The outage also took down people’s banks, which stopped many of them from doing things like buying groceries 💀
I don’t think saying it’s good for us “touching grass” is a good argument here when AWS hosts such a substantial portion of all online services.
CallMeAnAI@lemmy.world 4 weeks ago
How many banks didn’t work? Which ones? You have a source? Visa and MC were good all day here in the real world in the east coast.
Sounds like you’re just trying to exaggerate around an edge case that frankly isn’t the end of the world even if it were common for 4 hours a year
AmbitiousProcess@piefed.social 4 weeks ago
I can see why your account is marked with two red marks on PieFed for low reputation, because man do you come off confrontational.
Search engines exist. Use them before acting as if I"m making shit up.
The list of financial institutions that had issues, as far as I can tell from industry reporting and downdetector graphs, is Navy Federal Credit Union (~15 million members), Truist (~15 million customers), Chime (~8-9 million customers), Venmo (~60 million users), Ally Bank (~10 million customers), and Lloyds Banking group (~30 million customers).
Assuming no overlap, that’s nearly 140 million people that lost banking and money transfer access.
The outage lasted for 15 hours in some cases, due to many AWS services recovering after the outage, yet having a backlog to work through, which took many more hours. Many services also depend on AWS in a manner where AWS coming back online doesn’t instantaneously restart service. These systems are complex, and not every company that relied on them could instantly start back up the moment the main outage was resolved, let alone when many services were still marked as impacted for hours and hours later as they worked through their backlog.
I also blame them for not having additional redundancy. I blame both them for not having a fallback, and AWS for allowing such a major outage to happen. Shockingly, more than one party can be at fault.
jj4211@lemmy.world 4 weeks ago
I’m also skeptical that any payment processing networks were impacted. I would be surprised, but less so if they couldn’t manage their account online which might have similar effect. I’m not surprised at all of the grocery store or restaurants were significantly impacted. I know a lot of the apps were broken and I could imagine someone used to apping everything leaving their cards at home and unable to get lunch. Might have some aggressively “modern” establishments that are kiosk only and I could imagine them getting downed by aws outage.
I’m told that a lot of the companies did all the right things but still got taken down because some dependent Amazon services are tethered to that single DC and only Amazon has the power to change that.
CallMeAnAI@lemmy.world 4 weeks ago
I’ll wait for the final root cause but…
We mitigated most of it by swapping to secondary DNS and completely taking any thing related to AWS DNS and services in useast1. If you didn’t have secondary DNS and heavily reliant on AWS internal DNS this might be something they experienced.