37
OT: The MS issue and what caused it (lemmy.ml)
submitted 13 hours ago by to c/selfhosted@lemmy.world
33 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 7 hours ago* (last edited 2 hours ago) (3 children)

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.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 5 points 5 hours ago

    but 12-24hrs of downtime every few years seems like a highly reliable system

    1. We don't call it o351 because it has '12-24hrs of downtime every few years'.
    2. In the enterprise space, the target is a few minutes each year.
  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 3 hours ago

    There's a lot more downtime than that. It's just that most of them are limited in size or scope, and don't generate headlines. I'm pretty sure their service status page is public. Services are frequently degraded for a subset of users.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 hours ago

    rolling your own can have pretty small downtime. The biggest issue in the past was places did not want to spend on hardware that did not do anything but take over. Also disk failure was the most common big issue which is way lower with ssd's. it does not take a whole lot of spend to keep downtime away but so many places want to pinch every penny.

  • permalink
  • fedilink
  • source
  • parent