What the Recent Airline, Banking and Microsoft Outages Teach Us About Business Resilience
In one week, this November, the U.S. got a hard lesson in how much of daily life runs on technology, and how fast it stops when that technology fails.
- Thursday, November 12: a Microsoft 365 outage knocked out Outlook, Teams, and Copilot for organizations around the world. Full service did not return until Saturday.
- Friday, November 13: the FAA grounded every flight in the country for more than four hours after a communications failure in the air traffic control network. Thousands of flights were canceled over the next two days.
- Monday, November 16: a software bug at JPMorgan Chase delayed transactions for its own customers and for customers of other banks. Hours later, a separate system outage at United Airlines held departing flights at the gate for about 90 minutes.
Four outages in five days, in three vastly different industries. Here is the most important detail: none of them was a cyberattack. Each one started with something ordinary, such as an upgrade, a configuration change, a piece of old equipment or a software bug.
That is exactly why these events matter to manufacturers and distributors. If it can happen to Microsoft, the FAA, and the largest bank in the country, it can happen to your ERP, your network, or your warehouse systems. Here is what this week teaches us.
Lesson 1: Routine Changes Cause Big Problems
The FAA ground stop began with maintenance. According to the U.S. Department of Transportation, a contractor was replacing old copper lines with fiber at a remote site when a router began flooding the rest of the network. The Microsoft outage was traced back to a network change and server settings applied during an upgrade.
Neither was a dramatic failure. Both were planned work that did not go as planned.
What to do about it:
- Treat every change to your ERP, servers, network, and cloud tenant as a potential outage.
- Evaluate updates in a non-production environment before they touch live systems.
- Schedule changes outside your busiest production and shipping windows.
- Make sure every change has a written, tested rollback plan before it starts.
Lesson 2: Know Where Your Single Points of Failure Are
When Microsoft 365 went down, email, calendars, chat, and meetings went down with it for hundreds of millions of users. Reuters reported that some trading firms fell back to confirming trades by fax. Organizations that ran some Microsoft services on their own servers were somewhat spared.
The point is not that the cloud is risky. The point is that concentration is risky when nobody has thought about what happens if one provider stops working.
What to do about it:
- List every critical system your business depends on: ERP, email, phones, EDI, shipping, payroll, and banking.
- For each one, ask a simple question. If this stopped for a full day, what would we do?
- Look for backup channels that do not share the same failure point, such as a phone tree or text alerts that do not depend on Teams or Outlook.
Lesson 3: Your Partner’s Outage Is Your Outage
Chase said the issue was isolated to its own systems. Even so, customers at Bank of America, Wells Fargo, U.S. Bank, and others saw slow transactions whenever Chase was on the other side, and Zelle payments were delayed even though Zelle’s own network was working.
Manufacturers and distributors live in exactly this kind of web. Your operations depend on your bank, your carriers, your EDI partners, your suppliers, and your software vendors. If any one of them goes down, you feel it.
What to do about it:
- Map your outside dependencies, not just your internal systems.
- Ask key vendors about their own resilience and recovery plans.
- Know how to keep taking orders, receiving goods, and paying suppliers if a partner system is unavailable.
Lesson 4: Recovery Takes Longer Than the Fix
The FAA lifted its ground stop Friday night, but more than 2,000 flights were still canceled on Sunday. Planes and crews were in the wrong cities, and it took days to untangle.
Microsoft saw something similar. When engineers brought servers back online, returning traffic overwhelmed them again. They had to bring services back gradually, which stretched the outage past 24 hours.
The lesson is that fixing the problem and getting back to normal are two different things. A two-hour ERP outage can mean a full day of catching up on orders, picking, shipping, and invoicing.
What to do about it:
- Define how long each critical system can be down (your recovery time objective) and how much data you can afford to lose (your recovery point objective).
- Plan the catch up, not just the restore. Who re-enters orders, who confirms shipments, who talks to customers?
- Evaluate your backups by actually restoring them. A backup you have never restored is a guess, not a plan.
Lesson 5: Have a Manual Fallback
When the United system that helps pilots calculate aircraft weight went down, United held flights at the gate rather than fly without accurate numbers. That was the safe call, but it also shows how much modern operations depend on systems that used to be done by hand.
Your shop floor and warehouse are no different. If your ERP or scanners go down, can your team still pick, pack and ship? Do they know how?
What to do about it:
- Write simple downtime procedures for your most critical processes, such as order entry, shipping, receiving, and production reporting.
- Keep key reports, like open orders and pick lists, exported somewhere you can reach during an outage.
- Walk through the plan with your team at least once a year so nobody is learning it during a crisis.
Lesson 6: Aging Infrastructure Is a Business Risk
Federal officials pointed to old equipment as a major factor in the ground stop, with reports that the routers involved dated back to the early 2000s. The Transportation Secretary has called for billions in new funding to modernize the system.
Many mid-sized manufacturers and distributors have their own version of this: a server room nobody wants to touch, an ERP version that is years behind, network gear past end of support. It works until the day it does not.
What to do about it:
- Inventory your hardware and software and flag anything out of warranty or support.
- Build a realistic modernization roadmap instead of waiting for a failure to force it.
- Consider hosting critical systems, including Epicor, in a well-managed cloud environment with built-in redundancy and disaster recovery.
A Quick Resilience Checklist
Use these questions to see where your business stands today:
- Do we have a current list of critical systems and the vendors behind them?
- Is every change to production systems assessed, scheduled and reversible?
- Have we restored our backups successfully in the last six months?
- Do we know how long we can operate without our ERP, email, or phones?
- Do our people have written downtime procedures they have actually practiced?
- Is any key system running on hardware or software that is no longer supported?
If you answered “no” or “not sure” to more than one of these, it is time to take a closer look.
The Bottom Line
Outages are not a question of if, but when. This week showed that even the biggest, best funded organizations in the world can be stopped by an ordinary update or a single piece of equipment. The difference between a bad afternoon and a lost week comes down to preparation: knowing your dependencies, managing change carefully, planning the recovery and modernizing before old systems fail.
2W Tech helps manufacturers and distributors build that kind of resilience. We cover managed IT and network support, backup and disaster recovery, Microsoft 365 and Azure, cybersecurity, and Epicor hosting, all from one team that understands how your business actually runs.
Want to know how your business would hold up in an outage like this? Contact us at today to talk with our team.
2W Tech. Every Solution. One Partner.
Read More: