News for hackers. Stuff that matters.
Re:Chase Bank is now also having a meltdown by swozey on Monday November 16, 2026 @02:31PM (#50521905)
There's going to be a big swing to get off the cloud methinks, hopefully it benefits my career
Re:Chase Bank is now also having a meltdown by chrismustcode on Monday November 16, 2026 @02:36PM (#50521965)
Hows the cloud responsible for the outages in a way that is mitigated by self hosting in recent outages and this one?
Re:Chase Bank is now also having a meltdown by cube00 on Monday November 16, 2026 @02:40PM (#50522021)
Not needing to run at big tech scale makes self hosting easier.

You also have full control of downtime and recovery rather the refreshing the MSFT status page.

Re:Chase Bank is now also having a meltdown by ultrarunner on Monday November 16, 2026 @02:43PM (#50522078)
Presumably a central provider takes down your dependent services with no local ability to navigate around the outage. Removing the dependency obviates the outage risk. It introduces its own downsides as well, but that's a different discussion.
Re:Chase Bank is now also having a meltdown by swozey on Monday November 16, 2026 @02:56PM (#50522259)
Oh my precious
Re:Chase Bank is now also having a meltdown by cube00 on Monday November 16, 2026 @02:38PM (#50521990)
I doubt it, c-suite will never approve the spike capital expenditure for buying hardware now they're under a nice smooth subscription curve which doesn't harm their profits as dramatically.
Re:Chase Bank is now also having a meltdown by phatfish on Monday November 16, 2026 @04:58PM (#50523959)
I reckon, it would take 3 days of full outage for an average company to even consider the work needed to migrate from cloud providers or services. Obviously with some exceptions around risk to life systems, which should have an independent disaster recovery plan already.

M365 would have needed to be down for a full work week for job adverts to go out for an internal systems engineering team.