Over the past week, anyone could be forgiven for wondering whether a Diehard IV –style cyberwar had finally arrived in the US.
Across just four consecutive business days, a mass Microsoft exchange outage broke IT services for thousands of companies , a Federal Aviation Administration tech screw-up grounded airplanes across the country, a software problem affecting JPMorgan Chase caused another round of disruption, a United Airlines system glitch delayed flights yet again, and an NSA classified network’s downtime left the agency’s staff sitting at home waiting to return to their office at Fort Meade. In the midst of a US war with Iran and rising fears of AI-enabled hacking , this still-unfolding comedy of IT errors colliding across American infrastructure felt to plenty of observers like more than a coincidence.
Yet there’s still no evidence that any one of these clustered technological failures were related, much less caused by hackers. Their improbable, sequential timing left Americans anxiously doomscrolling for signs of foul play. But in cases like these, it’s the job of cybersecurity analysts (and reporters at WIRED) to determine—vibes aside—whether the latest tech outage was actually an accident or the result of a cyberattack.
The baseline for that fact-finding, as anyone tasked with investigating these incidents will tell you, is that the vast majority of these digital breakdowns are not the result of malicious intent but rather casualties of IT admins’ constant war to keep computer systems from collapsing under the weight of their own complexity.
“I’ve just seen enough times where we thought maybe it’s a cyberattack and it turns out it’s not. Sometimes it will be, but typically not,” says Matthew Prince, CEO of the Internet infrastructure company Cloudflare. “Right now, most of what we’re seeing is the standard background noise. Stuff breaks, and that’s just the nature of complex systems.”