folks,i know this is OT but i decided to post here as i’m sure there are a lot of people here that work in IT and know what thay are talking about. The recent MS failure is what i would like your opinion on.
from what I’ve seen, MS declared that a bunch of servers went offline and the load had to be spread on remaining servers. They fail to identify what caused the first bunch of servers encountering issues and they claim it was mot related to a hacker attack (why would they, it would lead to massive panic and distrust). So, then what caused the issue in the first place? Could it have been a piloted denail of service attack?
I’m sure the truth will emerge in coming days but was interested in the more tech savy people’s opinione. In the meantime i rejoyce for not having to depend of third party infrastructure at home, thanks to my little homelab.
A further consideration is that this does once again prove that companies that put all their eggs in one basket, are at yhe mercy of big tech. i experienced this personally at works where comunication by Teams and Outlooks was pretty much halted for hours.
The main reason for problems: Bad IT administration that relies way too much on Microsoft.
I blame Jensen’s leather jacket. It’s clearly way too powerful.
EDIT: There’s…a 3rd mistress now? Giggity.
By 2030 AI is gonna completely replace sysadmins as the cause of outages.
I’m sure it all came down to poor upper management decisions which they will try to blame on technology
Or on the poor lower level man that forgot to follow procedures …
this does once again prove that companies that put all their eggs in one basket, are at yhe mercy of big tech.
I am certainly no Microsoft lover, but 12-24hrs of downtime every few years seems like a highly reliable system compared to the cost of rolling your own software stack for the majority of companies.
If this event turns out to be a harbinger of what’s to come I’ll change my tune but I would be shocked if this single period of downtime led to a shift away from Outlook.
but 12-24hrs of downtime every few years seems like a highly reliable system
- We don’t call it o351 because it has ‘12-24hrs of downtime every few years’.
- In the enterprise space, the target is a few minutes each year.
I’m sure the truth will emerge in coming days but was interested in the more tech savy people’s opinione.
Why speculate when you will get it dfrom the horses mouth in a couple days?
But my 2¢ is a bad code being deployed.
a bad code
just one?
- ‘a code’ - a password
- ‘code’ (mass noun) - programming instructions, for example
Upper management should do things and moves to avoid bad code deploying.
Why should upper manglement have a say in this? They only thing any manglement should say is Yes to a digital twin for a test environment to catch crap like this before it becomes a global outage.
Preventing expensive accidents is a part of survival strategy. Should be interesting topic for any CEO and every level of management. In reality they just hope accidents won’t happen?
I think it is a cascading effect some unmaintained and forgotten server gave out causing others to fall.
Thats what think not based on any facts.
I worked at a place that was running COBOL written in the 1970s that supported thousands of other services across the globe.
it was not redundant. it was not HA. there was just one.
the man who wrote the software died in 1995.
nobody understood what it did, or how to maintain it.
I would say, with the recent layoff from Microslop, your assessment might be more accurate than most think.
I doubt Microslop would pass up the opportunity to blame a hacker group or AI at this point. they look like a bunch of incompetent assholes. since they are being vague about it, and won’t immediately state a root cause, that can only mean it’s incompetence.
At the moment, we can only guess. My guess: an update (maybe of a load balancer) went wrong. We will never know for sure.
Maybe this is theproblem with big tech. They will never confess and what strikes me is that businesses and governments just won’t wake up
All I can say for sure, is that nobody knows for sure.




