Three Outages in Five Days: What Microsoft, the FAA, and the Bank Disruptions Can Teach TPRM Teams

5 minute read

November 2026

by Kaitlyn Frank

In the span of five days, three separate disruptions reminded millions of people how much of daily life runs on technology they never see. On Thursday, November 12, a Microsoft 365 outage took down Outlook, Teams, and Copilot for more than 24 hours across at least 74 countries. On Friday, November 13, the Federal Aviation Administration (FAA) halted departures at every U.S. airport for more than four hours. And on Monday, November 16, customers at many major banking giants reported trouble accessing accounts and sending payments.

None of these incidents were a cyberattack. Microsoft traced its outage to a network capacity upgrade. Transportation Secretary Sean Duffy tied the FAA ground stop to overloaded routers connected to maintenance work by a contractor. Early indicators in this week’s banking outages described the problem as a technical bug. For Third-Party Risk Management (TPRM) teams, that’s the real lesson: The disruptions that hit your business hardest often start with a routine change at a vendor you depend on, or at a vendor your vendor depends on.

What Happened, and Why It Spread

The Microsoft outage is the most familiar kind of third-party disruption. Organizations from hospitals to airports run email, collaboration, and increasingly their AI tools on Microsoft 365, so a single provider issue stopped work for thousands of companies at once. Most of those companies have Microsoft on their vendor inventory. Far fewer know which of their other vendors, from outsourced help desks to claims processors, also run their operations on the same platform, all of which went dark at the same time.

The FAA ground stop shows how deep that chain can run. The FAA reported a communication issue affecting all of its Air Route Traffic Control Centers, which led to more than 10,000 flight delays and over 1,300 cancellations. The cause pointed back through a contractor to network equipment in its care. Airlines, travelers, and every business with people on the road absorbed the impact of a failure several layers removed from them.

The bank disruptions add one more layer. Users flagged Zelle on outage trackers, but Zelle said its network was operating normally and that delays stemmed from problems at individual banks. The root cause remained hard to determine, with one major bank saying its own systems weren’t directly affected, yet its customers could still see delays sending money to other institutions. When services share a network, a problem at one participant becomes everyone’s problem.

Your Vendor Inventory Is Only the First Layer

Most TPRM programs do a solid job cataloging direct vendors. Fourth-party risk, the risk introduced by your vendors’ own vendors and technology, is where visibility usually stops. That gap matters most during an outage, when the first question from leadership is “Are we affected?” and the honest answer depends on relationships you may never have mapped.

Closing that gap starts with knowing which critical third parties rely on which cloud providers, payment networks, telecom carriers, and software platforms. With that map in place, concentrated risk becomes visible before an incident rather than during one. If a dozen of your critical vendors all run on the same cloud region or the same core banking processor, that’s a single point of failure worth knowing about, and planning around.

Speed Is the Difference Between an Incident and a Crisis

Every one of this week’s outages rewarded the organizations that could answer the exposure question quickly. Teams with a current view of their vendor network could identify affected services, reach out to the right third parties, and activate continuity plans within the hour. Teams without one spent that hour building a spreadsheet.

A fast, repeatable response usually comes down to a few practical steps:

  1. Map critical fourth parties. Capture the cloud, payment, and infrastructure providers your most important vendors depend on, and keep that information current as part of ongoing monitoring.
  2. Tier vendors by operational impact. Know which third parties support processes your business can’t pause, so outreach goes to the right vendors first.
  3. Pre-build incident outreach. Keep a short, ready-to-send questionnaire that asks affected vendors about impact, workarounds, and recovery timelines.
  4. Validate continuity evidence. Review business continuity and disaster recovery documentation for critical vendors before an outage tests it.
  5. Close the loop afterward. Update vendor risk profiles with what you learned, and revisit contract terms and service-level commitments where gaps showed up.

The Same Muscle Applies to Vulnerabilities

Outages and vulnerabilities ask TPRM teams the same question: Which of my third parties are exposed, and how fast can I find out? This week’s disruptions came from technical failures, but a newly disclosed vulnerability in a widely used product spreads through vendor networks the same way. The organizations that respond well are the ones that already know which vendors run the affected technology.

That’s the problem ProcessUnity CVE Monitoring is built to solve. When a new vulnerability emerges, including those added to the Cybersecurity and Infrastructure Security Agency (CISA) Known Exploited Vulnerabilities (KEV) catalog, CVE Monitoring identifies which of your third parties are exposed so your team can focus outreach on the vendors that actually need it. Instead of sending a blanket questionnaire to your entire portfolio and waiting days for answers, you start with a targeted list and act while the threat is still fresh.

Outages like the ones this week aren’t going away, and neither are new vulnerabilities. TPRM teams that understand their full vendor network, including the fourth parties behind it, are the ones ready to respond in minutes instead of days.

To see how ProcessUnity helps teams find third-party exposure fast, explore CVE Monitoring or contact the ProcessUnity team for a demo.

Frequently Asked Questions

Fourth-party risk is the risk introduced by your vendors’ own vendors, such as the cloud providers, payment networks, and software platforms your third parties rely on. Fourth-party risk often goes unmapped, which makes it hard to tell during an outage whether your business is affected.
They show how a single failure at one provider can cascade across thousands of organizations at once. For TPRM teams, these events highlight the need to map fourth-party risk and concentration risk so you can quickly identify which vendors and business processes are exposed.
Start with your critical vendors and ask which cloud, infrastructure, payment, and software providers they depend on. Capture that information in your assessments, keep it current through ongoing monitoring, and look for shared dependencies that point to concentration risk.
Confirm which of your third parties and fourth parties are affected, prioritize those supporting critical processes, send a short pre-built impact questionnaire, and activate the relevant continuity plans. Teams that have already mapped fourth-party risk can complete these steps far faster.
ProcessUnity CVE Monitoring identifies which of your third parties are exposed to newly disclosed and actively exploited vulnerabilities. That gives TPRM teams a targeted list for outreach, so they can address fourth-party risk tied to vulnerable technology quickly instead of surveying every vendor.

Related Articles

About Us

ProcessUnity is the Third-Party Risk Management (TPRM) company. Our software platforms and data services protect customers from cybersecurity threats, breaches, and outages that originate from their ever-growing ecosystem of business partners. By combining the world’s largest third-party risk data exchange, the leading TPRM workflow platform, and powerful artificial intelligence, ProcessUnity extends third-party risk, procurement, and cybersecurity teams so they can cover their entire vendor portfolio. With ProcessUnity, organizations of all sizes reduce assessment work while improving quality, securing intellectual property and customer data so business operations continue to operate uninterrupted.