On November 13, the FAA halted departures across the country for more than four hours. Officials say there’s no indication of a cyberattack. The trouble started during a network upgrade, and the agency said its older equipment became unstable.
You don’t run an air traffic system. But if you run a business in San Marcos, Carlsbad, or anywhere in North County, you’ve probably lived a smaller version of this story: an update that took down a system on a busy morning, a new device that didn’t get along with an old one, or a vendor outage that stopped your team cold.
As technology grows more complex, we believe incidents like this will become more common, not less. The question isn’t whether technology will cause you a bad day. It’s how ready you’ll be when it does. The good news is that the steps that help most aren’t complicated.
What happened with the FAA ground stop?
Here’s what officials have said publicly so far. The FAA and its network contractor were in the middle of an upgrade, converting the communications network from copper wire to fiber optic. Officials have pointed to router activity at two facilities, one in El Dorado, Arkansas, and one in Amarillo, Texas. From there, things cascaded. 17 of the FAA’s 22 Air Route Traffic Control Centers experienced network instability, and the agency said its older equipment became unstable when data began flooding the network at a rate of 1,000 connection attempts every four to five seconds.
Some things are still open. The FAA hasn’t determined the root cause. Investigators are weighing defective equipment against an installation or configuration error, and the manufacturer’s parent company says its equipment was working as configured. Officials have said there’s no indication of a cyberattack or outside threat. As of November 17, the FAA is pausing new router installations while it investigates.
Whatever the final cause turns out to be, the pattern is one IT professionals know well: older systems struggling when something around them changes, and a problem in one place spreading to many. The lesson isn’t to avoid upgrades. It’s that change is where older systems are most exposed, so change deserves a plan.
Why are IT incidents making headlines more often?
Businesses, and the public services they rely on, run on more technology than ever. That means more software, more connected devices, more outside vendors, and more upgrades happening all the time. Every one of those can fail, be misconfigured, or be attacked. Older systems are being modernized while still in use, which adds risk right where old meets new. And when one vendor or system sits underneath many others, a single problem can ripple a long way.
None of this means technology is getting worse. It means we depend on it more, so when it stumbles, more people notice.
What does this look like for a small business
You don’t need to be an airline to feel it. Here are versions we see all the time:
- A new firewall or switch that doesn’t get along with an older device
- A software update that knocks out a system on a busy morning
- A cloud service or vendor outage that stops your team from working
- A server migration that breaks a line-of-business app nobody remembered
- A change at one location that ripples out to the rest
Most of the time, the damage comes less from the problem itself than from not being ready for it. Downtime costs more when nobody knows who to call, what to do next, or how long recovery will take.
7 steps to start preparing now
You don’t need a 30-page plan. A short, consistent set of habits goes a long way.
- Know what you depend on. Keep a simple list of your key systems, apps, and vendors, including the older ones that “just work.” If you can’t list them, you can’t protect them.
- Back up your data, and test the restore. A backup you’ve never restored from is a hope, not a plan. Keep copies separate from your main systems, and try recovering a file or two on a regular schedule.
- Write a simple downtime plan. Decide ahead of time who to call, how your team keeps working if a key system is down, and how you’ll tell employees and customers what’s going on. One page is plenty.
- Plan changes before you make them. Before any upgrade, list what it touches, roll it out to one device or location first, keep the old configuration backed up, and have a rollback plan. Give someone the authority to pause if something looks off.
- Keep systems updated, with care. Updates matter for security, but timing and testing matter too. Avoid month-end and payroll days, and roll updates out in stages when you can.
- Lock down access. Turn on multi-factor authentication, keep admin accounts to a minimum, and remove access when people leave. Compromised accounts are a common way attackers get in.
- Practice and review. Spend 30 minutes walking your team through “what if our main system went down tomorrow?” Revisit your plan every few months and whenever you add new software.
Try this quick test: if your most important system went down tonight, would your team know who to call, what to do next, and how long recovery would take? If any answer is “not sure,” that’s where to start.
Where a managed IT provider fits
You can do a lot of this on your own. But some of it is hard to do well from inside a busy business, and it’s exactly where a managed IT services provider earns its keep:
- Mapping your environment, including the forgotten legacy systems, so risks are known before a change touches them
- Change management: reviewing what an update or migration affects, testing it first, rolling it out in stages, and keeping a rollback ready
- Backups that are actually tested, not just scheduled
- Proactive monitoring, so problems are caught early instead of discovered by your staff
- Vendor coordination, so when something breaks, one team is working the problem instead of everyone pointing at someone else
- A documented response plan, so the first hour of an incident isn’t improvised
The FAA situation is a reminder that even large organizations with dedicated teams and contractors can be caught when change and older systems collide. Having someone whose job is to plan for that, before it happens, is the difference between a short interruption and a lost day.
The bottom line
Outages are going to happen. What you control is how much they cost you. Know what you depend on, test your backups, write a one-page downtime plan, and treat every change as something to plan, stage, and be able to undo.
IT TechPros helps businesses in San Marcos, Carlsbad, Oceanside, Escondido, Poway, and greater San Diego prepare for the unexpected and keep their systems running. Want to find out how ready your business really is? Get in touch and we’ll help you figure out a practical starting point.
Frequently asked questions
Why are IT outages making headlines more often? Most of daily life and business runs on connected technology, so when something fails, more people feel it. In our view, that trend is likely to continue.
What caused the FAA ground stop? Officials have pointed to router activity during a network upgrade, but the FAA says the root cause hasn’t been determined and the investigation is ongoing.
Was the FAA ground stop a cyberattack? Officials have said there’s no indication of a cyberattack or outside threat.
Does my small business really need a downtime plan? If your team relies on your network, servers, or cloud apps to work, yes. Even a one-page plan can prevent a lot of confusion and lost time.
What should an IT outage plan include? Your key systems and vendors, who to call, how work continues during downtime, how you’ll communicate with staff and customers, your backup and restore steps, and a schedule for reviewing it.
Sources
Details about the FAA ground stop come from public reporting current as of November 17, 2026. The FAA’s investigation is ongoing, and details may change.
- FAA: Nationwide Ground Stop: Questions and Answers (November 15, 2026)
- CNN: FAA pauses Juniper router installations after nationwide ground stop
- Axios: FAA pauses tech upgrade linked to nationwide ground stop
- ABC News via Yahoo: FAA halts router installation following nationwide ground stop
- Fox Business: Monday air travel faces key test after FAA ground stop as possible cause emerges
- The Hill: What to know about the Arkansas router that led to the FAA groundings

