What an anxious week taught me about separating the real concerns from the noise
I haven’t slept well this week. And I know I’m not alone. We all lived it. Flights were stopped across the whole country, the banks were having trouble, Apple and Microsoft went down, even the NSA’s own network went dark, and in the middle of it the FBI put out a warning about a powerful new hacking tool. I found myself doing what I suspect a lot of people were doing: adding it up and wondering whether it was connected, whether somebody had planned it. I wondered that more than once — and even my Garmin alerted me that I was not calm about it.
A cybersecurity expert has said that people he has not spoken to in 15 to 20 years are calling him in a panic, certain the power grid is about to go down. I recognize myself in that. I too have wrestled with a question that has no clean answer: how much of my time and energy belongs to preparing for something that might never happen, and how much belongs to simply living my life? This week it felt as if the worst had arrived to collect. Each scary scenario had a different set of preparations involved, and I did not know which way to turn.
When I remembered the motto that I have lived by since I was a little girl in a Brownie uniform: Be Prepared. It has been the Girl Scout motto for more than a century, and it has been mine for most of my life. Sitting with it, I realized that the motto has never once said be frightened. A healthy sense of preparation is a good place to land — prepare in measure, keep it in its proper size, and then go live your life. So I took inventory, and I did my best to be prepared.
From that steadier place, I did what preparation actually asks of a person. I slowed down, and I checked each frightening outage one at a time, on its own evidence. I did not assume that they were unconnected. I looked for the connections honestly, for any consistency or thread running between them. Each time I dug into one, I found a separate, ordinary reason: a software bug in a bank’s own hardware, an update a company pushed to its own systems, a security patch that broke the network that it was meant to protect. No thread held. They were not one story, and nobody had to plan them.
The air traffic failure was different, though. It had a story underneath it, reported in pieces, months apart, and only now beginning to be put together. Now, I’m not an engineer, and I will not pretend to explain the equipment. But the story underneath this one is not about equipment. It’s about management and good judgment. Last December, the government handed oversight of the air traffic control rebuild to a company called Peraton. Peraton does not do the hands-on work; it is paid to manage the companies that do. Before the award, the FAA’s own reviewers rated Peraton’s financial condition “high risk.” The competitor was rated “low risk.” The normal purchasing rules were waived. Peraton got the job anyway. The mandate was called “No Excuses,” and it demanded and rewarded unprecedented speed.
One finding in the government’s own audit caught my attention. There was no single master schedule tying thousands of projects together — more than 11,000 individual schedules, not yet integrated into one. I don’t need to understand telecommunications equipment to recognize why that is alarming. If nobody can see the whole undertaking in one place, it’s not being managed. The auditors also warned that putting speed first could lead to disruption. Whether that contributed to Friday’s failure has yet to be established. Then, after the failure, the administration raised its request to $50 billion — for air traffic control and airports — and it wants the vote rushed through the Congress that is about to leave. You have to look at it closely to realize that the increase does not include the control system that failed. When the rules are waived at the start and the warnings are overruled at the start and the response to failure is a request for more money, that is a concern with specific, documented reasons behind it. That concern is real.
Here’s what I’ve landed on, and it’s bigger than one program or one frightening string of days. Fear grows fastest in a pile-up, when everything frightening arrives at once and the internet is happy to help us stay frightened — the floating theories, each one feeding the next. The way out is not to stop caring, and it is also not to spend life on worry. We must look at each issue rationally, one at a time, and test whether the connections are real. We must be concerned about the things that hold up under checking, and give them our full attention in our just-in-case preparations. We can’t let the other things be a distraction.
Sources
- U.S. Government Accountability Office — “Air Traffic Control Systems” (GAO-26-107992, September 2026)
- FAA — “Nationwide Ground Stop: Questions and Answers”
- Reuters — “FAA says air traffic control overhaul management contract worth $1.5 billion” (February 11, 2026)
- FactCheck.org — “Unpacking the Partisan Finger-Pointing Over FAA Funding” (November 2026)
- Senate Commerce Committee Democrats — letter to Secretary Duffy and Administrator Bedford (November 16, 2026)
- CNN — Erin Burnett OutFront interview with David Kennedy of TrustedSec (November 17, 2026)
- FBI — FLASH-20261113-001, “Threat Overview of ARTEX Autonomous Penetration Testing Framework” (November 13, 2026)
- The Independent — “Chase Bank outage causes issues for customers at other major US banks” (November 17, 2026)
- TechCrunch — “Apple services, including iCloud, App Store and Apple Music, hit by outage” (November 17, 2026)
- Expert Insights — “Microsoft Traces Global 365 Outage to a July Fix That Its Own Failover Spread” (November 16, 2026)
- Fox Business — “Jay Clayton addresses concerns amid widespread tech outages” (November 17, 2026)
- Fox News (opinion) — “The outages America has suffered weren’t an attack, but the next failure could be” (November 18, 2026)

Leave a Reply