Skip to content
Back to Insights

When the tools you rely on stop working

By Aisha · 19 November 2026 · 5 min read

This week was a lot. In the space of a few days, some of the biggest names in tech went down one after another, and two attacks showed how easily trouble can come in through a supplier. I want to go through what happened, and then answer the question I asked on LinkedIn: if your email or card machine went down tomorrow, what would you do?

The outages

It started last Thursday, 12 November, when Microsoft 365 went down. After the first 16 hours or so it was mostly Exchange that was still broken, which is the part that runs Outlook email. For a lot of businesses that meant most of a day without email. Microsoft says it wasn’t an attack and has put it down to a software fault in its own servers. Everything was back to normal by the morning of the 14th.

Then it kept going. Workday had problems on the 13th. On Sunday the 15th, part of Amazon Web Services had sign-in and connection errors for over three hours, and AWS runs a huge share of the websites and apps we all use. On Monday, a software bug at JPMorgan Chase held up payments, and customers at several other big US banks couldn’t get into their accounts. United Airlines had a software problem the same day that hit the apps its crews and pilots need before take-off. In the US, flights were grounded across the whole country for a while. On Tuesday, Apple’s iCloud and Apple Pay played up, and Apple blamed an internal update.

From what’s been reported so far, none of these were attacks, and none of them are linked to each other. A lot of it was just updates and changes that went wrong.

The attacks

On Monday, someone found a weakness in Optimizely, a tool big companies use to test changes on their websites, and used it to add malicious code to their pages. A security researcher, Scott Helme, found it on 178 organisations’ sites, including Zoom, IKEA, HSBC and the BBC. The code tried to skim card numbers, steal cookies and swap crypto wallet addresses for the attacker’s own. None of those companies were hacked directly. The code came in through a tool they’d added to their own websites.

Closer to home, TfL took its Oyster photocard website offline after a breach that may have exposed the details of around 265,000 customers. It noticed when people who already had accounts started getting emails asking them to create one. Names, addresses, dates of birth and security questions and answers may have been taken. TfL says passwords and card details weren’t. If you have a photocard account, TfL is asking you to change your password and pick a new security question.

What I’d do if I ran a small business

The thing these stories have in common is that the businesses affected didn’t do anything wrong themselves. Something they relied on stopped working, or got used against them. You can’t stop Microsoft having a bad day. What you can do is make sure a bad day for them isn’t a disaster for you. Here’s where I’d start.

Write down what you depend on. Make a simple list of the outside services your business can’t run without: email, card machine, booking system, accounts software, website, phone line. Next to each one, note who provides it and what you’d do if it stopped for a day. This is the most useful hour you’ll spend this year, and most small businesses have never done it.

Have a second way to reach your customers. If email goes down, could you still contact people? Keep an up-to-date export of your customer contact list somewhere that doesn’t depend on your email provider. A phone, a text, or a quick update on your social media can tell people you’re still open.

Know how you’ll take payment without your card machine. Find out whether your terminal can work offline, and what the limits are. Have a backup, such as a payment link you can send by text, or a second provider. Decide in advance whether you’ll take cash or IOUs from regulars.

Keep a copy of tomorrow. If you run on bookings or appointments, print or export the next day’s list at the end of each day. If the system’s down in the morning, you still know who’s coming in.

Know what’s running on your website. The Optimizely attack worked because the code was loaded from someone else’s tool. Ask whoever built your site which plugins, scripts and third-party tools it loads. Take out anything you don’t use any more, and make sure the rest are kept up to date.

Be extra careful during an outage. Scammers love a big outage. Expect emails and texts that say “click here to restore your account” or “reset your password”. Go to the company’s own website or status page instead of clicking the link.

Sort out your own accounts. Use a different password for every account, ideally with a password manager. Turn on two-step verification wherever it’s offered. And if a site asks for a security question, you don’t have to give the real answer. Treat it like another password and store it with the rest.

Where Cyber Essentials fits

Cyber Essentials is the UK government-backed scheme that covers the basics: keeping software up to date, controlling who has access to what, using firewalls and malware protection, and setting devices up securely. It won’t stop a Microsoft outage, and it isn’t a business continuity plan. But it does close off a lot of the easy ways in, and it makes you look at what you’ve got and who looks after it. The government has also just announced a 75 per cent discount on Cyber Essentials certification for small businesses getting their first certificate.

If you’d like help writing your list, or working out where to start, you can book a call with me.

Aisha