Microsoft, Apple, Banking and US Air Traffic Outages: What UK Businesses Can Learn From a Week of Disruption
A week of disruption across Microsoft, US air traffic control, banking and Apple has exposed how dependent businesses are on connected services. What can UK organisations learn from it?
Several major providers have experienced disruption in the space of a week. For UK businesses, the priority is to understand which critical activities depend on external services, agree workable alternatives and make sure staff know what to do when those services aren't available.
Is it just us, or does it seem like every other day has come with some version of an outage at the minute? Whatever it is, it's really putting the NO in November. I mean, first it was an entire Microsoft outage, then US air traffic control, then banking services and, last night, Apple.
Over the past week, a series of high-profile outages has disrupted everything from workplace email to flights, online banking and consumer services. For those of us watching on from the sidelines, it's been a very stark reminder that even the biggest names in technology and infrastructure aren't immune to things going wrong.
Now, that doesn't mean the cloud is unreliable, or that every outage is a cyber attack, or even like it's a Covid 2.0 type pandemic, as some internet whisperings will have you believe, but it does mean that the services we depend on are often more interconnected than they appear.
And when one of them goes down, the question quickly becomes less about which system has failed and more about what your business can still do without it.
What's happened with the recent outages?
On the 12th and 13th of November 2026, a Microsoft outage affected services worldwide, including organisations and public services in the UK. Outlook and other Microsoft 365 services were among those affected, and it made for a chaotic Friday for millions of us.
Later on that same Friday the 13th of November (a very apt date for things to go wrong, right?), a telecommunications failure affecting US air traffic control prompted the Federal Aviation Administration to issue a nationwide ground stop. Departures were later allowed to resume, but the disruption led to thousands of cancellations. The FAA's account of the incident makes clear that this was a precautionary ground stop, not a claim that every aircraft already in the air was grounded.
And then, we had a much more normal Saturday and Sunday, only for Monday the 16th of November to bring up technical problems at JPMorgan Chase that disrupted banking services in the US.
As if that wasn't enough chaos for a month, let alone a five-day stretch, Apple experienced outages affecting services including the App Store, Apple Music, Apple Pay and AppleCare on Tuesday the 17th of November. Apple said an internal update had caused disruption, with Associated Press reporting on the separate incidents.
Microsoft 365
Outlook and connected Microsoft services experienced widespread disruption, affecting businesses and public services.
US air traffic control
A telecommunications failure led the FAA to temporarily stop departures nationwide.
JPMorgan Chase
Technical problems disrupted banking services in the United States.
Apple services
Services including the App Store, Apple Music, Apple Pay and AppleCare experienced disruption.
These hiccups all occurred at different organisations, with a myriad of unique systems and individual circumstances, and a run of outages close together doesn't, by itself, mean they're connected, that a cyber attack is responsible, or that it's the end of the internet and we should all panic. At all.
And all of that's before we mention any Fortune 500 CEOs who were ousted.
In short, it probably leaves more than a few businesses begging for some form of normality, while crossing their fingers and toes to hope they're not next up in the firing line.
Although, in what is a brilliantly wicked form of irony, as I'm writing this, yet another critical vulnerability has been discovered, this time in Java, which is the world's third-largest programming language.
But for UK businesses, the more useful connection is operational: when a service is unavailable, the effects rarely stay neatly inside the IT department. As we saw on Friday, it can grind your organisation to a halt if the wrong thing goes down at the wrong time.
Why do IT outages have such a wide impact?
Most, if not almost all, businesses don't rely on one system at a time; they rely on a chain of them.
I mean, if you look at your own as an example, an employee might need an internet connection, a working device, an identity service and access to Microsoft 365 just to reach the information needed for a customer call.
Your finance team may depend on a banking platform, an approval process and an accounting application to pay suppliers. Equally, a customer-facing website might rely on several services behind the scenes, some of which the business has never dealt with directly.
When just one link in that chain fails, the impact can travel further than expected.
That was also evident in October 2026, when a Google Cloud data centre power failure affected a range of customers, including UK financial firms. The Bank of England reported disruption to some customer-facing banking and payment services, as well as internal systems.
It's not necessarily that organisations have chosen the wrong suppliers. Often, it's that they haven't mapped how much depends on them, and they don't have a failsafe in place to fall back to.
What should a business do during an IT outage?
Start by confirming what's affected and using a trusted source for updates. Then decide which business activities need an alternative way of working, who will coordinate the response and how staff and customers will be kept informed.
In practice, that means:
Confirm what's affected
Check the provider's service status and contact your IT team or support partner. A problem affecting one person may need a different response from a wider provider outage, for example.
Avoid unnecessary changes
Repeated password resets, configuration changes or attempts to restore systems while the cause is unclear can add confusion.
Agree when to update people
Set a time for the next internal update, even if there's no resolution yet.
Use an agreed alternative channel
If email or collaboration tools are unavailable, use an alternative communication method that staff already know and can access securely.
Keep a record
Record affected work, decisions and any manual transactions so they can be checked when services return.
An outage can also create a perfect opportunity for scams, so be cautious of unexpected messages claiming to offer a fix or asking staff to sign in urgently. Use known contact details and official status pages rather than links in unsolicited messages.
Business continuity starts with the work, not the technology
A business continuity plan doesn't need to begin with a long list of servers and software. It should begin with the activities the organisation needs to keep moving.
Can you take customer orders? Pay staff and suppliers? Access the information needed to deliver a service? Contact the people responsible for making decisions? Contact anyone?
For each critical activity, identify the systems and suppliers it relies on, how long disruption would be tolerable, and what a workable fallback looks like. The answer may be different for each team.
For example, a temporary manual order log might help a sales team keep track of enquiries. Finance may need an agreed process for prioritising payments and checking them before submission. Customer service may need an approved message and a separate way to contact key clients.
A workaround invented halfway through an outage is much harder to trust. Make sure the people responsible for critical work know which alternatives have been approved before they're needed.
Backups matter, but they won't fix every outage
A backup helps you recover data, but it doesn't automatically make an unavailable application, login service or banking platform work again, which is important.
A business may have a good copy of its files but still be unable to access the system people use to work with them. Equally, restoring data unnecessarily during a temporary provider outage can create duplicate or conflicting versions.
The National Cyber Security Centre recommends keeping an independent copy of important cloud data and knowing how to access and restore it.
For business continuity, it's also worth checking whether the people who need that information can reach it during the specific disruption you're planning for.
Keep any offline or alternative copies appropriately protected, limit access and agree how changes will be reconciled once normal service returns.
Test the plan before you need it
A plan that says "contact IT" is a start, but isn't much help if the contact details are stored in the email system that's just gone down.
Run a short scenario with the people who'd be involved. Ask: what happens if Microsoft 365 is unavailable for a working day? Who decides which activities take priority? How do you contact staff? Where are customer commitments recorded? What happens when the service comes back?
You don't need to duplicate every platform or build an expensive second environment, but it's useful to know where a disruption would hurt, which alternatives are realistic and who owns the next step.
That's where an internal IT team and an external partner can work together: one understands the business's priorities; the other can help test the technical dependencies and recovery options.
The takeaway
This week's outages aren't a reason to abandon trusted platforms, although it's a stroke of misfortune that yet another vulnerability has been unearthed as we're writing this.
They're a reminder that no provider can make a business continuity plan on your behalf. Only you know what's most important to you and your business.
The strongest starting point is a straightforward conversation: which parts of the business can't wait, what do they depend on, and what will people do when those services aren't available?
At Fifosys, we help organisations connect those business priorities with their IT, cloud and security decisions. If recent disruption has raised questions about your own dependencies, talk to our team.
IT outages and business continuity FAQs
Why have so many major services experienced outages?
The incidents described in this article affected different organisations and systems. Their proximity doesn't establish a common cause. What they demonstrate is how widely disruption can spread when businesses and customers depend on connected technology services.
What should a business do first during an IT outage?
Confirm the scope of the problem, check the provider's official service status and contact your IT team or support partner. Identify the business-critical activities affected, agree an owner for the response and establish a reliable way to update staff and customers.
Does having cloud backup protect against a service outage?
Cloud backup helps recover data, but it doesn't usually restore access to a provider's unavailable platform. Businesses should distinguish between data backup, disaster recovery and business continuity, and understand what their arrangements cover.
What should a business continuity plan include?
It should identify critical activities, the systems and suppliers they depend on, acceptable downtime, agreed alternative processes, communication routes and the people responsible for decisions. Plans should be accessible during an outage and tested regularly.
Should businesses replace cloud providers after an outage?
One outage doesn't automatically justify replacing a supplier. Businesses should review the impact, their dependencies and the available alternatives before deciding whether changes to the provider arrangement or continuity plan are needed.
Prepare your business for the next disruption
From understanding your cloud dependencies to testing continuity and recovery arrangements, we can help you make practical decisions about keeping critical business activities running.
Talk to our team
Discuss the risks, dependencies and continuity arrangements that matter most to your business.
Explore backup and disaster recovery
Understand how to protect important data, plan for disruption and improve recovery readiness.