The CrowdStrike outage: what one bad update taught every business
Last Friday, millions of computers around the world suddenly crashed to a blue screen and refused to start again. Airlines grounded flights. Banks and payment systems stumbled. Hospitals postponed appointments. Some TV broadcasters went off air. And the cause wasn't hackers — it was one faulty software update.
If your business runs on computers, card machines or cloud systems — and almost every business does now — this is a wake-up call worth paying attention to.
What happened
On 19 July 2024, cybersecurity company CrowdStrike pushed out a faulty content update for its Falcon security software, which runs on Windows computers at many large organisations. The update caused those computers to crash with the infamous "blue screen of death" and get stuck in a restart loop.
Microsoft estimated that about 8.5 million Windows devices were affected. That's a small share of all Windows computers in the world, but they were concentrated in big organisations that run critical services — which is why the disruption was so widespread.
Important points:
- It was not a cyberattack. It was a bug in a routine update from a trusted security supplier.
- Fixing it was slow and manual. In many cases, IT staff had to physically go to each affected computer and restart it in a special recovery mode to remove the faulty file.
- The ripple effects lasted days, as airlines cleared backlogs and organisations worked through thousands of machines.
Why this matters for small businesses
You might think, "We don't use CrowdStrike, so it's not my problem." But the real lesson isn't about one company. It's about how dependent every business has become on technology we don't control — and what happens when it fails.
Your business may depend on:
- A point-of-sale system
- A card machine or mobile money platform
- An accounting or invoicing app
- Cloud email and file storage
- WhatsApp, Facebook or an online store
- An internet connection and electricity
Any one of those can fail. The question is: what do you do when it does?
Lesson 1: Have a business continuity plan
A business continuity plan is simply a written answer to "what do we do if X stops working?" It doesn't need to be a thick document. One or two pages covering your most important systems is enough to start.
For each critical system, write down:
- What happens if it goes down?
- How will we keep serving customers?
- Who is responsible for what?
- Who do we call for help?
Lesson 2: Don't rush every update
Updates are important — they fix security holes and bugs. But this outage showed that updates themselves can cause problems. Large organisations use staged updates: test on a few machines first, then roll out more widely.
For a small business, that might mean:
- Not updating every computer at once
- Avoiding major updates right before a busy period like month-end or a sale
- Knowing how to roll back if something goes wrong
Lesson 3: Back up everything
If a computer won't start, is your data safe? Make sure you have regular backups of your important files, customer records and accounts — ideally one copy in the cloud and one stored separately. And test them: a backup you've never restored is a backup you can't trust.
Lesson 4: Keep manual fallbacks
When the systems failed, some airlines went back to handwritten boarding passes. Ask yourself what your low-tech fallback is:
- Paper receipt books for when your POS is down
- An offline price list so staff can still quote and sell
- Printed contact lists for key suppliers and customers
- A cash float for when card machines fail
- Alternative payment options, like mobile money or bank transfer
Load-shedding has already taught many southern African businesses this lesson. We wrote about it in keeping your business online during power cuts.
Lesson 5: Watch your supplier concentration
When one supplier powers a large share of the world's critical systems, one mistake can cause global chaos. The same happens on a small scale: if one supplier, one platform or one person holds the keys to your business, you're exposed.
Where you can, spread your risk — a second internet connection, a backup payment method, more than one way to reach customers.
Lesson 6: Have a customer communication plan
During the outage, the organisations that coped best were the ones that told customers what was happening, quickly and honestly. Prepare:
- A short message template for "we're experiencing technical issues"
- The channels you'll use — WhatsApp status, Facebook, SMS, a sign on the door
- Who has permission to post updates
Customers are surprisingly forgiving when you keep them informed.
Your quick continuity checklist
- List your critical systems and who supports each one
- Write a one-page "what if it goes down" plan
- Set up automatic, tested backups
- Print a price list and key contact list
- Keep a receipt book and cash float on hand
- Have at least two ways for customers to pay
- Prepare a customer message template
- Avoid big updates before busy periods
- Know who to call for IT help, and save their number offline
Conclusion
The CrowdStrike outage wasn't caused by criminals or a natural disaster. It was a routine update that went wrong — and that's exactly why it's so instructive. Things will fail. The businesses that suffer least are the ones that planned for it.
Need help building reliable systems, backups and automated customer updates? Talk to us.
Want help putting this into practice?
Book a free 15-minute chat and we’ll show you the simplest next step for your business.
Let’s talk





