Incident sheet · /infrastructure

Filed
Read
3 min · 671 words
Severity
Routine

Two Weeks of Outages Hit FAA, Microsoft and Apple Pay

The FAA's nationwide grounding — the third since 9/11 — capped two weeks of outages at Microsoft, Apple Pay and NASA. Experts blame AI-accelerated patching colliding with legacy hardware.

These tech outages are giving Y2K, AI agent style
FeedThese tech outages are giving Y2K, AI agent style — haruudu / pixabay

Event log

  1. The FAA grounded all U.S. flights for hours, only the third time since 9/11.
  2. A Microsoft outage took down Outlook, Teams and Copilot for nearly two days.
  3. The DNI said the outages do not appear linked to state-sponsored terrorism.
  4. The failures came weeks after 'Black October' security incidents hit PHP, Node.js and LiteLLM on October 21.
  5. Preliminary findings point to FAA telecom modernization overwhelming legacy hardware.

The FAA grounded every flight in the United States for hours — only the third such nationwide stoppage since 9/11 — in a two-week stretch that also took down Apple Pay, NASA's internal communications, and Microsoft's Outlook, Teams and Copilot for nearly two days.

Banking platforms and productivity suites joined the list. The pattern was tight enough to look coordinated. It was not, according to the companies themselves, which attributed the failures to technical issues rather than cyberattacks or AI-driven intrusion.

The timing still raised eyebrows. The failures landed weeks after what the industry called "Black October," a cluster of unrelated security incidents on October 21 that hit PHP, Node.js and LiteLLM, among others.

Was this an attack?

No, by every official account so far. The Director of National Intelligence said the outages do not appear related to state-sponsored terrorism, and President Trump called them "individual events."

The anxiety was understandable. Hackers had recently compromised fridges in a grocery store and a blood bank in France. But the mechanism here appears to be internal, not hostile.

Dave DeWalt — an investor with more than three decades in cybersecurity, a former president and CEO of McAfee and former vice chairman of the CISA Advisory Council at the Department of Homeland Security — told TechCrunch the outages are most likely the "growing pains of a security system that's getting stronger, not weaker."

In his framing, AI tools such as Mythos are "surfacing vulnerabilities at a speed and scale we've never had before." Many of these flaws always existed. AI simply finds them faster than enterprises are used to, and the resulting rush to patch is what breaks things.

"That surge in patching is disrupting things in the short term," DeWalt said.

What actually broke at the FAA?

Anusha Iyer, a software engineer and founder of security startup Corsha, points to the collision between legacy and modern systems as the real story.

"These industrial systems were never designed to be connected, let alone securely connected in the way we are pushing them to be today," she said.

Preliminary findings, she noted, suggest the FAA outage occurred during a modernization of the agency's telecommunications infrastructure. The new technology likely ran at normal modern capacity. The legacy hardware underneath could not keep up, and parts of it failed.

So AI is taking blame it may not deserve, in her view. "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."

Virginia Senator Mark Warner, vice chair of the Senate Intelligence Committee, reached a similar conclusion while 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.

What should enterprises do now?

Both experts offered concrete guidance:

  • Adopt AI more deliberately, with more testing and a clear priority order for what gets fixed and when, DeWalt said.
  • Segment industrial systems more tightly and apply stricter access controls, Iyer said, so modern components can be phased in with risk mitigated at each step.

Is there upside?

DeWalt sees one. He would rather U.S. enterprises find and patch their flaws in this messy fashion than let adversaries discover and exploit them in AI-driven warfare with national security consequences.

He also expects a founding wave in "AI-driven vulnerability management, autonomous remediation, safe patch testing and deployment, and resilience for the systems that keep critical infrastructure running."

"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 lesson for CIOs is plain: the outages were self-inflicted integration stress, and the fix is sequencing, not speed.

via techcrunch.com (Source)

Filed under

  • faa-outage
  • legacy-systems
  • infrastructure-modernization
  • ai-vulnerability-management
  • operational-resilience
Share this article:

More from Amara Osei

Amara Osei

Show full bio

Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.

203 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›