>

That’s what ya get
Someone at Microsoft incorrectly configured a router on their global WAN, causing an outage on their services. >

It's really crazy the more you work in IT the more you realise how stuff is literally hanging together by threads.
I always picture it as a game of Kerplunk where you're constantly removing one of millions of straws and hoping a marble doesn't fall >

These networks are all built with resiliency in mind. Just in mind.
Those straws really eat into the bottom line... >

some non-essential worker was fired in the 10k layoff, who was keeping afloat all services, hehe >

"Bob always said: "don't remove these lines" but hey Bob is not there anymore so let see..."
"crap"
"Someone has Bob's phone number... no the private one I mean..." >

I used to maintain decades old critical production code. It contained comments like "what the hell does this do? Don't remove, everything breaks if you do" and "relies on exploting a bug in perl 4.1.2. Don't upgrade!". >

Nightmare fuel. 
Imagine what those devs went through to find all that out! >

I'm sure you all know the monkeys story, my colleague in the US told me that story a dozen of times. Just in case here it is:
"In a facility they introduce a first group of monkeys. There are bananas attached on the sealing, when they rush toward them sprinklers activate and soak them with water.
Then they introduce a second group of monkey, when they try to rush toward the bananas the first group block them so they will not be sprayed with water...
Finally, the first group is removed and a third group is added. When they try to rush toward the bananas the second group block them.
The second group has never been sprayed by water but they block the third group not knowing why... except that the first group showed them not to do."
In a lot of companies now there is only the second and even only the third group of monkey now... >

And in some companies you're about 20 monkeys deep at this point. >

In some companies the monkey train goes so deep, they need management clearance before changing a single bit. >

I hope that includes answers.microsoft, Save people reading a useless thread, only to put "+Reddit" into their search  to get an actual answer >

i honestly don't know why people bother posting questions on there, all the so called experts just read from a script and post the same "useless solutions" over and over.
no better than ringing up for help with isp or phone probs.
"let me run our tests...."
​
we found no fault, thanks for calling. click. >

It's because 90% of the issues are picnic. >

Is that like pebkac? >

Yup problem in customer not in computer. >

Never heard that one before, brilliant. >

Hmm, maybe they fired the wrong workers? >

I dont understand any of this. >

Come on, I’m here scrolling bc I can’t sleep and now I just learn work tomorrow is going to be impossible. >

It's already gotten better after an hour of difficulties this morning >

I mean the issues have been there for 1 months time..... im in IT and we have had issues with some issues, affecting login into Teams / Office 365 Programs also... since 1st January.. 
only last week we saw an article posted advising problems but still not official from Microsoft >

Y23K problem >

23K?  That was back when the 40k universe was actually nice to live in! >

Someone accepted the update didn't they >

This was so fucking annoying today. >

Azure Devops was down also. >

And how! Incredibly slow all day >

They never should have moved Milton to the basement