Skip to the content
Five Days, Six Disruptions: What Business Leaders Should Take From a Rough Week

Five Days, Six Disruptions: What Business Leaders Should Take From a Rough Week

About the Author

Don Douglas
Don Douglas
Don Douglas is a Sr. Cloud Solutions Architect and specializes in assisting clients with evaluating and architecting cloud-based solutions to modernize, optimize, and secure their digital assets.

If the past week left you uneasy, you’re in good company. In the span of five days, email and collaboration tools went dark for businesses around the world, every departing flight in the country was held on the ground, customers at several of the nation’s largest banks couldn’t see their balances or move money, and visitors to some of the most trusted websites on the internet were served malicious code. 

We’ve heard the same question from clients, partners and, frankly, our own families: Is this all connected? Is somebody behind this? 

It’s a fair question. Here’s what we know, what we don’t, and what we think it means for organizations like yours. 

What Caused This Week’s Microsoft 365, FAA, bank and Optimizely outages?

Thursday, November 12 — Microsoft 365. Exchange Online, Outlook, Teams and Copilot became unavailable or unreliable for users in dozens of countries, and service wasn’t fully restored until the morning of Saturday, November 14. Microsoft’s preliminary explanation is that a problem introduced during an earlier network capacity upgrade surfaced after a more recent network change. Servers began failing health checks and dropping out of service, and the ones left standing couldn’t carry the load. Microsoft has said plainly that the outage was not related to a cyberattack. Its full post-incident review is still to come. 

Friday, November 13 — The FAA ground stop & Amtrack booking down. Shortly before 4:00 p.m. Eastern, the FAA halted departures nationwide with roughly 3,500 aircraft in the air. The stop lasted more than four hours—the longest since 9/11—and cancellations rippled through the weekend. The FAA says its legacy telecommunications equipment became unstable when its network was flooded with data, and that its network contractor had been installing a new router at one of the sites involved. Based on the evidence so far, the FAA says there is no indication of a cyberattack, though the root cause is still under investigation. That same evening, Amtrak’s booking systems went down for several hours with what the railroad described as a network outage, just as demand for travel alternatives surged. 

Monday, November 16 — Banks and United. Customers at Chase, Wells Fargo, Bank of America, U.S. Bank, Truist and others reported trouble logging in, checking balances and moving money, including delayed Zelle payments. JPMorgan Chase attributed the disruption to a software bug in an on-premises hardware system, said it was not cyber-related, and noted that other banks receiving its slowed transactions may have felt the effects. Later that afternoon, United Airlines held departing flights for more than 90 minutes because of what it called a widespread system outage—again, with no indication of a cybersecurity cause. 

Monday, November 16 — Optimizely. This one was an attack. Someone exploited a flaw in Optimizely’s Web Experimentation platform—a tool many companies use to test and personalize their websites—and planted malicious code that Optimizely’s own servers then delivered to visitors of at least 178 organizations, including CNN, the BBC, Zoom, Salesforce and HSBC, states Report URI. Over the course of the day, that code swapped cryptocurrency wallet addresses, tried to capture card details typed into payment forms, and attempted to deliver exploit kits to some iPhone users. Optimizely says the flaw has been fixed and the code removed. What stands out is that the affected companies weren’t the point of entry. A trusted vendor was. 

Are The Recent Outages Connected, Or Was It A Coordinated Cyberattack?

We understand why “it was just a bug” is hard to accept when the bugs keep coming. Skepticism is healthy. But we’d encourage leaders to hold two ideas at the same time. 

First, based on everything publicly available today, there is no evidence connecting these events to each other or to a coordinated attack. Each organization has offered a different, specific explanation. Some of those explanations are still preliminary, and more will be known as final reviews are published. Until then, the honest answer is that we don’t know everything—and neither does anyone speculating online. 

Second, the absence of an attack doesn’t make the week any less instructive. Look closely and a common thread appears: several of these failures reportedly began with routine, well-intentioned change—a capacity upgrade, a router replacement, a software update. In tightly connected systems, a small change can travel a long way. As industry analyst Patrick Moorhead put it, “When one piece fails, it fails at national scale.” 

How Do Attackers Take Advantage of IT Outages?

Within hours of the Microsoft outage, phishing emails began circulating that impersonated Microsoft service notices. They cited the real incident number and warned that “held” messages would be deleted unless the recipient clicked a link. Microsoft’s own threat intelligence team flagged the campaign. 

The tactic is effective for a simple reason: during an outage, people are stressed, waiting for answers and primed to act on anything that looks official. Attackers don’t need to cause the disruption. They only need to show up while everyone is confused. 

A convincing fake notice usually has a few things in common: a real, publicly reported incident for credibility, a deadline or threat of data loss, and a link or attachment as the “fix.” 

How To Verify Notice Before Acting On It

Go to the source directly

Check the vendor’s official status page, which you should already have bookmarked, rather than clicking a link in an email.

Treat urgency as a warning sign

Threats of deleted messages or locked accounts are designed to rush you.

Confirm through a second channel

If a notice asks you to log in, pay or change a setting, verify it by phone or through your IT team or provider.

Report it

Forward suspicious messages to your security team so others aren’t caught by the same email.

Remind your team before the next outage, not during it.

Why Will IT Outages Become More Common as Patching Speeds Up?

There’s another force at work that deserves attention, separate from last week’s specific events. To be clear, nothing made public so far suggests any of those outages were caused by rushed security patching, and we aren’t suggesting they were. But it is shaping what the months ahead will look like. 

Attackers are now using AI to find and weaponize software flaws at a pace we haven’t seen before. Industry research published this year found that newly disclosed vulnerabilities are being exploited within hours of disclosure, not the weeks defenders could once count on. The federal government has taken notice. In June, CISA ordered federal agencies to fix the most dangerous vulnerabilities within as little as three days, citing attackers’ use of AI as a key driver. 

That changes the math for everyone: your own IT team, your software vendors, and the largest cloud providers in the world. The old rhythm of waiting for a monthly maintenance window, testing a patch for a few weeks, and rolling it out on a quiet weekend is giving way to something faster: patch early, patch often. Security teams are increasingly accepting a hard trade-off. It’s better to accidentally break something while protecting it than to be breached because you moved too slowly. 

We think that’s the right call. But it comes with a cost worth naming honestly. More change, made faster, means more chances for something to go wrong. As the industry adjusts to this new pace, we expect disruptions to key systems and services to become more common, not less, even at the most capable providers. For business leaders, the question is shifting from “How do we prevent every outage?” to “How do we keep running when one happens?” 

What Questions Should Business Leaders Ask About Outage and Vendor Risk?

Most of the organizations we work with will never run an air traffic control network or a global bank. But nearly all of them rely on the same patterns that were on display this week: a handful of cloud platforms, a growing list of third-party tools, and systems that are constantly being changed and updated. A few questions worth asking around your own leadership table: 

  • If email and Teams were unavailable for a full business day, how would your people communicate—and how would customers reach you? 
  • Do you know which outside scripts and tools run on your website, especially on pages where customers enter payment or personal information? 
  • How are changes to your critical systems tested, rolled out in stages, and reversed if something goes wrong? 
  • Would your employees recognize a convincing “service notice” that isn’t real, and do they know how to verify one? 
  • When a key vendor has a bad day, how quickly would you know, and what happens next? 

None of these require panic or a big budget. They require attention, and an honest look at where you depend on others. 

How Can A Business Keep Operating When Cloud Systems Go Down?

If more frequent disruptions are part of the landscape now, resilience has to be planned rather than hoped for. These are the practices we see make the biggest difference: 

  • Define your minimum viable operations.
    Decide ahead of time which few processes must keep working no matter what (taking orders, paying people, serving patients, shipping product) and what the manual fallback is for each. 
  • Have a way to reach people that doesn’t depend on the system that’s down.
    An out-of-band text or call tree, with contact lists kept somewhere other than your email, is simple and invaluable. 
  • Keep your plans where you can reach them.
    An incident response plan saved only on the file share that just went offline isn’t much of a plan. Keep a copy offline, even on paper. 
  • Treat vendor outages as “when,” not “if.”
    Know where each critical provider posts status updates, who on your team watches them, and what you do in the hours before an official update arrives. 
  • Rehearse.
    A one-hour tabletop exercise (“Email and Teams are down until tomorrow. Go.”) will reveal more gaps than any binder on a shelf. 
  • Expect the scam that follows the outage.
    After any major disruption, remind employees that attackers will impersonate the “fix,” and that any urgent request to click, log in, or pay should be verified another way. 

When Should a Business Start Preparing for IT Disruptions?

Weeks like this one are unsettling, and anyone who says otherwise isn’t paying attention. But they’re also a reminder that resilience isn’t built in the middle of a crisis. It’s built in the ordinary weeks before one.  

Weidenhammer has been helping organizations navigate technology change for nearly 50 years—through the arrival of networks, the internet, the cloud and now AI. If the past few days have raised questions for your team, you don’t have to sort through them alone. We’re always glad to talk.