What kinds of disruption did organizations see, and how did their IT teams get things running again?
What was the CrowdStrike outage like for organizations dealing with it?
Answers
For affected organizations, entire Windows machines could end up stuck on a blue screen, including servers and workstations. That meant internal applications could go down along with the computers people needed to access them.
The cause and a way to remediate it became clear relatively quickly, though accounts differ on how soon official fix steps were available. The bigger problem was getting the fix onto every affected machine. A straightforward manual procedure gets a lot less straightforward when hundreds or thousands of devices need attention.
Reply to this answer
The physical logistics were brutal. Machines spread across a large distribution site are one problem. Remote devices with no local IT support, including point of sale systems, are another.
Some teams enlisted and trained other staff to help with recovery. Getting enough hands to the right places could matter as much as understanding the technical fix.
Reply to this answer
It also depended heavily on whether an organization used CrowdStrike and which of its systems were affected. Some were back in a few hours. Others faced disruption for days, and the outage reached critical operations such as airports.
Some teams even managed to block CrowdStrike updates early enough to prevent additional systems from crashing, although that was not a recovery method for machines already affected.
Reply to this answer
One unsettling part was seeing lots of systems blue-screen at once without knowing why. That can look like a major security incident at first. Once the cause was understood, teams could switch from figuring out what was happening to getting machines back into service.
Reply to this answer
It was different from an outage where a cloud provider has to restore the service. In the CrowdStrike incident, affected IT teams had hands-on recovery work they could do. That gave them a path forward, but also left them with a huge amount of work to coordinate.
A separate Azure regional outage occurred around the same time and affected some airline systems. The two disruptions can get mixed together when people recall that period.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_w84+quavelo.2:
So knowing the fix didn't necessarily mean the organization was close to being back up?
9x!drimvori_284:
Right. Critical systems might come back first, while the rest still needed people to reach and work through each device.