bestill
Well-Known Member
- Joined
- Dec 26, 2013
- Messages
- 8,984
- Reaction score
- 65,719
Watching this now -I saw an article re him before all this happened.
All smiley. I don't suppose he's smilng much right now.
I feel sorry for him.
Watching this now -I saw an article re him before all this happened.
All smiley. I don't suppose he's smilng much right now.
I feel sorry for him.
snipped.How embarrassing. An Aussie is President of Crowdstrike.
Maybe that is why we had so many outages.
A favorite method that men are known to use is the yelling and cussing.Come to think of it the turn it off and on has been around way before the internet.
I've used that method ages ago with appliances, sometimes it worked.
If it didn't work, I had two other methods.
One I call my "whack whack" method where I give the gadget a hard whack
The other is a good talking to "if you don't fix yourself by morning, you're going in the rubbish bin!"
I have had varying degrees of success with all three methods.
The librarian at my high school insisted that the computers only worked properly if she swore at them.A favorite method that men are known to use is the yelling and cussing.
That method is sometimes successful.
And that's how kids learned interesting vocabulary back then.
There also was the ever-popular approach of Fix Until Rendered Useless.A favorite method that men are known to use is the yelling and cussing.
That method is sometimes successful.
And that's how kids learned interesting vocabulary back then.
I disagree. My company had a major IT call at 5:30pm CST on Thursday as a lot of our applications were failing. About 2 hours in, it was determined that Microsoft Azure was having issues and it was all hands on deck trying to re-route thingssnipped.
I think it was a timing thing. The outage began around 11 PM in NYC. By the time the U.S. woke up on Friday the fix was known and IT staff were already implementing it. In contrast the outage hit at 2 PM in Sydney and there wouldn't even be anything anyone could do all afternoon until CrowdStrike could figure out how to mitigate the problem.
I disagree. My company had a major IT call at 5:30pm CST on Thursday as a lot of our applications were failing. About 2 hours in, it was determined that Microsoft Azure was having issues and it was all hands on deck trying to re-route things
snipped.
I think it was a timing thing. The outage began around 11 PM in NYC. By the time the U.S. woke up on Friday the fix was known and IT staff were already implementing it. In contrast the outage hit at 2 PM in Sydney and there wouldn't even be anything anyone could do all afternoon until CrowdStrike could figure out how to mitigate the problem.
BBM: Thank you for explaining that part! When I saw the instructions somewhere telling users how to reboot the computer etc I thought "Really?!" lol. Now I see that it was more complicated.I was specifically referring to the CrowdStrike crash while it sounds like you're talking about a separate incident that occurred with Microsoft's Azure cloud.
These are actually two separate problems that occurred back-to-back. The first brought down Azure services in the Central US region. That occurred on Thursday, and was just being resolved as the CrowdStrike crash occurred. They were apparently unrelated, and it was just coincidence that they happened one right after the other.
I believe this was the worst outage that MS has ever had, but it was localized to computers that were accessing Azure servers from that one region. Companies that had built redundancy in their operations were able to function despite the outage. In comparison, the CrowdStrike incident affected computers worldwide and there was almost nothing any company could have done to avoid the crash.
That’s sketchy as F - Microsoft is piggybacking off the crowdstrike issue like nothing to see here folks. *face palm*I was specifically referring to the CrowdStrike crash while it sounds like you're talking about a separate incident that occurred with Microsoft's Azure cloud.
These are actually two separate problems that occurred back-to-back. The first brought down Azure services in the Central US region. That occurred on Thursday, and was just being resolved as the CrowdStrike crash occurred. They were apparently unrelated, and it was just coincidence that they happened one right after the other.
I believe this was the worst outage that MS has ever had, but it was localized to computers that were accessing Azure servers from that one region. Companies that had built redundancy in their operations were able to function despite the outage. In comparison, the CrowdStrike incident affected computers worldwide and there was almost nothing any company could have done to avoid the crash.