Two Weeks of Outages Hit FAA, Apple Pay, Microsoft — AI Y2K?
FAA groundings, Apple Pay, NASA and Microsoft outages hit within two weeks. Officials rule out cyberattacks, but experts see AI surfacing flaws faster than legacy systems can absorb.
By Olivia Hart
4 min read

What's News
- FAA grounded all U.S. flights for hours — only the third time since 9/11.
- Microsoft outage took down Outlook, Teams and Copilot for nearly two days.
- October 21 'Black October' incidents hit PHP, Node.js and LiteLLM weeks earlier.
- DNI says outages don't appear tied to state-sponsored terrorism; Trump called them 'individual events'.
- Ex-McAfee CEO Dave DeWalt expects startups in AI-driven vulnerability management and autonomous remediation.
The FAA grounded every flight in the United States for hours — only the third such nationwide stoppage since 9/11 — inside a two-week window that also took down Apple Pay, NASA's internal communications, and Microsoft's Outlook, Teams and Copilot for nearly two days.
That is the scale of the disruption now sitting on the desks of American corporate and government technology leaders. Airline booking systems, banking platforms and productivity tools — the plumbing of everyday commerce — failed in quick succession, and nobody has yet offered a single unified explanation.
The companies themselves say the outages were not cyberattacks or AI attacks, but ordinary technical failures. President Trump called the issues "individual events." The Director of National Intelligence said the outages do not appear related to state-sponsored terrorism, according to TechCrunch's reporting.
The official line, in short: nothing to see here. The timing, however, makes that line hard to sell.
Why does the timing matter?
The failures clustered within a short timespan of each other — and only weeks after what the security industry dubbed "Black October," when a slew of unrelated cybersecurity incidents struck PHP, Node.js, LiteLLM and other core software projects on October 21.
Coincidence is possible. But the pattern has drawn comparisons to a Y2K-style systemic event, accelerated by AI rather than a date change. That comparison comes with a caveat: no evidence published so far ties any of these incidents together, and investigations remain underway.
What do the experts actually believe?
Dave DeWalt — a cybersecurity investor with more than three decades in the field, including as president and CEO of McAfee and vice chairman of the CISA Advisory Council at the Department of Homeland Security — thinks the outages are probably AI-related, though not in the way casual observers assume.
The outages are most likely the "growing pains of a security system that's getting stronger, not weaker," he told TechCrunch, adding that "AI is surfacing vulnerabilities at a speed and scale we've never had before through AI tools like Mythos and others."
His argument runs counter to the hacker-invasion narrative. Many of these technical flaws have always existed, DeWalt says. AI tools are simply finding them faster than enterprises are used to, and companies are rushing to patch them before bad actors can exploit them.
"That surge in patching is disrupting things in the short term," he said.
Was the FAA outage AI's fault?
Not according to Anusha Iyer, a software engineer and founder of security startup Corsha. She frames the moment as legacy systems meeting modern ones — badly.
"These industrial systems were never designed to be connected, let alone securely connected in the way we are pushing them to be today," she told TechCrunch.
On the FAA specifically, preliminary findings point to a modernization effort: the agency was upgrading its telecommunications infrastructure, and the transition overwhelmed legacy hardware. The new systems likely ran at normal modern capacity. The old hardware could not keep up.
"It's not rapid adoption of AI yet causing these outages," Iyer said. "The fault is the rushed mix of the legacy and modern systems without a clear understanding of operational and cyber risk or the ability to gatekeep and protect the legacy systems."
So AI is getting the blame for failures that predate it. That is a convenient story for vendors — and one that independent investigations have not yet confirmed.
What are lawmakers saying?
Virginia Senator Mark Warner, vice chair of the Senate Intelligence Committee, reached a similar conclusion while noting investigations continue.
"These disruptions should serve as a wake-up call. It feels like every day brings another reminder that AI is moving faster than our ability to manage its consequences," Warner wrote on X.
His statement assigns responsibility to management, not malice — but it stops short of naming what specifically went wrong, which nobody has yet done publicly.
Where is the business opportunity?
For corporate technology buyers, the prescription from both experts is unglamorous: more testing, tighter segmentation of legacy industrial systems, stronger access controls, and phased introduction of modern systems so risk can be contained at each step.
DeWalt said he would rather see U.S. enterprises find and patch their flaws in this messy fashion than have adversaries exploit the same vulnerabilities in AI warfare with graver national security consequences.
He also expects a wave of new startups focused on:
- AI-driven vulnerability management
- Autonomous remediation
- Safe patch testing and deployment
- Resilience for critical infrastructure systems
"There's real pain in this transition as we've seen in the past week," DeWalt said. "But there's also enormous opportunity for the companies that help organizations move at AI speed without breaking things."
The takeaway for operators: the outages exposed how little margin legacy infrastructure has left, and the vendors who can close that gap — safely, and with evidence — will find a market that just became urgent.
Original: businessinsider.com
More from Olivia Hart
Show full bio
Staff writer covering people, launches and day-to-day practice in entrepreneurship, startups and venture funding at Business Bearings.
2,440 articles