Cybersecurity

It Wasn't Hackers. It Was a Router in Arkansas.

Two weeks of big outages, and the internet knew exactly who did it. It was none of them. It was us.
some rolled up copper wire
Published November 19, 2026 • 4 min read

Everybody calm down

Over the last two weeks, Microsoft 365 went down, the FAA grounded every domestic flight, Chase got slow, United got stuck, iCloud and Apple Pay took a nap, and the NSA lost its own internal network. If you were on social media, you know exactly who did it. It was China. Or Russia. Or a teenager in a hoodie. Or all three, working together in a dark room with green text scrolling down the walls.

It was none of them. It was us. It's almost always us.

The official list of suspects

Here's what the companies themselves say broke:

To be fair, real attacks did happen this month. Hackers abused a signup flaw at Optimizely and planted malicious JavaScript that Report URI tied to 178 organizations' sites. Hospitals, libraries, schools, and at least one town in Maine got hit with the usual ransomware-flavored misery. But the big, scary, everything-is-down outages? Those were self-inflicted.

The call is coming from inside the data center

Anyone who has worked in software for more than a week knows the most dangerous thing in any system isn't a hacker. It's a change. A config push, a capacity upgrade, a "quick" maintenance window, an update that passed every test in staging because staging has the traffic of a rural Blockbuster.

Microsoft's outage is the textbook case. The bug shipped months earlier and did nothing. That's what latent means: it waits. Then some unrelated change shifted traffic, and the old bug finally had the load it needed to ruin everyone's Thursday. No single change was the problem. Two harmless changes, months apart, were the problem.

A few lessons, none of them new, all of them apparently still necessary:

The hackers showed up anyway

Here's my favorite part. The day after Microsoft's outage, attackers sent fake Microsoft 365 "service health" emails that used the real incident ID. The pitch was that the emails held during the outage would be deleted within 24 hours unless you clicked a link.

So the hackers didn't cause the outage. They just waited for it, like a guy selling umbrellas outside the subway when it starts raining. That's the real security lesson of the month. Attackers don't need to break your systems when your systems break on their own and everyone's already confused and clicking things.

So, should you panic?

No. But if you get an email this week saying your outage-delayed messages are about to be deleted, maybe don't click it. And if you work in IT, go hug your change management process. It's been through a lot.

As for the cause of the next big outage, I'll make a prediction right now. It won't be a foreign government. It'll be a Tuesday afternoon config change that somebody described in the ticket as "low risk."


Christopher McLain
chris@nearauth.ai