Federal officials told a House committee on Wednesday that they had found no evidence linking the November 2026 tech outages to a coordinated or malicious cyberattack. Lawmakers, some commentators and at least one senior official want to know whether artificial intelligence played a part. By Friday, the fight had reached the White House, which had replaced its national cyber director. The outages hit airlines, major banks, Microsoft 365 and Outlook, Apple products and an NSA network, and an hours-long nationwide FAA ground stop disrupted airports.

What caused the November 2026 tech outages, according to officials

Officials told a House Homeland Security hearing on Nov. 18 that they had found no evidence linking the outages to a coordinated or malicious cyberattack, according to CBS News. Homeland Security Secretary Markwayne Mullin said he was highly confident that foreign adversaries were not behind the failures, but he admitted he had never seen this many outages in such a short period. Patch quoted him saying he was "98 percent confident that this has nothing to do with our adversaries hacking or going after our systems."

Director of National Intelligence Jay Clayton offered a more technical account. "these are separate service outages associated with maintenance and technical changes," he testified, according to Fox News.

Witnesses repeatedly pointed to patching rather than hacking. None of them said the patches were prompted by AI finding vulnerabilities, CyberScoop reported.

Why AI keeps surfacing in the outage debate

Mullin told Fox News that he believed "super intelligence" was behind the failures. Fortune reported that AI appears partly responsible, a view that differs from the maintenance explanation offered at the hearing.

Lawmakers were more direct. CyberScoop reported that industry and government officials in Hill briefings blamed patches for AI-discovered vulnerabilities. A Fox News live blog said a top Democratic senator argued AI was contributing to the outages, while Rubio said the incidents were not connected.

The backdrop is a steady stream of serious software flaws. A security firm revealed a critical Java flaw on the Tuesday before the hearing, after a serious PHP vulnerability was disclosed in October, according to Cybersecurity Dive. Earlier reporting also noted that Google had warned autonomous AI agents can keep attacking systems without rest, per The Epoch Times.

The argument critics make runs like a chain. AI tools find flaws faster, vendors ship fixes faster, and rushed updates break things. That chain may hold, but none of the reporting reviewed here documents it. A separate USA 24 report on GAO covert tests that got ChatGPT, Claude, Gemini and Grok to plan attacks raises a different question from what caused these outages.

Microsoft's July bug and the rest of the outage list

Microsoft gave the most specific cause so far. It said its nearly 24-hour disruption came from a software bug introduced in July, plus higher network traffic and reduced server capacity, and that the incident was not related to cyber or AI agents, according to Fortune. Reporting described the broader wave as lasting about 10 days.

Affected service What reporting shows Cause or status
Microsoft 365 and Outlook Nearly 24-hour disruption Software bug introduced in July, plus higher traffic and reduced server capacity, per Microsoft
Major banks Customers directly affected Not specified in reporting reviewed
Apple products Affected during the wave Not specified in reporting reviewed
Government communications system for commercial aviation Affected during the wave Not specified in reporting reviewed
Nationwide FAA ground stop Hours-long, disrupted airports Not specified in reporting reviewed

The FAA and L3Harris were still investigating root causes when the reporting was published. Officials describe the failures as unconnected, which means each affected system may have its own explanation.

Cairncross out, Davies in: what changed at the White House

The White House removed National Cyber Director Sean Cairncross on Nov. 19, and CNN reported the move that day. CBS News and CNN both reported that Chief of Staff Stephen Miller pushed for the decision. CNN framed the removal as the latest in a pattern of cyber leadership departures, following last year's firing of the NSA director and deputy director.

Pentagon CIO Kirsten Davies was named as his replacement. She will need Senate confirmation to hold the post permanently, and the timing of that vote is not yet known.

The White House has said it has no indication the outages were coordinated, state-sponsored or caused by a malign actor, according to CNBC. Its background briefing described the outages as results of upgrades to legacy cyber systems, the Fox News live blog reported.

The personnel change does not settle the cause question. The administration tells Congress the failures trace to routine maintenance and aging systems, while lawmakers want to know whether AI-discovered flaws changed how fast patches reach networks. Whoever holds the cyber director job will have to reconcile both positions in front of Congress.

Which parts of the cause remain unresolved

  • AI's role is disputed. Officials cite maintenance and patching, Mullin and some commentators point to AI, and Microsoft says its outage had nothing to do with AI agents.
  • Clayton's account is reported differently. Al Jazeera reported that he said the outages likely stemmed from organizations using AI to fix security flaws, which differs from his testimony describing maintenance.
  • Root causes remain open for the FAA and L3Harris, according to Fortune.
  • Davies's Senate confirmation timing is unknown.

President Donald Trump told a Fox reporter on Thursday, Nov. 19, according to Al Jazeera: "Tell them to relax, everything is good, these are individual events." That reassurance does not explain how a 10-day wave of outages reached airlines, banks, Microsoft services and an NSA network.

What to do if your bank, airline or email goes down

No consumer can patch a vendor's servers, but a few habits limit the damage when a service disappears. These are general steps, not recommendations from officials.

  • Keep copies of boarding passes, account statements and insurance cards somewhere you can open offline.
  • Save a second phone number or alternative contact channel for your bank and airline before you need it.
  • Check the vendor's official status page during an outage instead of relying on social posts.
  • Read your bank's liability terms. USA 24 has reported that five US banks now make customers liable for losses from outside AI agents.

Business owners have a different checklist:

  • Ask vendors whether patches install automatically, on what schedule, and whether you get notice before major changes.
  • Write a rollback plan for software updates and test it before the next patch cycle.
  • List which workflows depend on Microsoft 365 or Outlook, and set up a manual fallback for approvals and customer messages.

What comes next for AI rules, markets and Senate hearings

On Nov. 19, Reps. Don Beyer (D-VA), Sara Jacobs (D-CA) and Celeste Maloy (R-UT) released an outline of the SAFE AI Act. It would require frontier AI developers to publish safety frameworks, report incidents and submit to evaluations, according to the office of Rep. Don Beyer. It is an outline, not a formal bill, and it is not yet known which committee would take it up. FourWeekMBA describes the proposal as 14 rules for AI labs.

The incoming chair of the Senate Homeland Security Committee is preparing hearings on AI safeguards, per AI Weekly. Whether those hearings will address the outages is still developing.

Markets added pressure that week. NPR described AI stocks and broader markets as pummeled, and Asian markets fell sharply on Friday on AI bubble fears, according to AI Weekly. USA 24 has reported that the Federal Reserve now sees the AI buildout as an inflation and stability risk, a backdrop that raises the stakes of any AI-linked failure.

Four things will show whether this becomes a cyber story or an AI policy story. Watch for root-cause findings from the FAA and L3Harris, any follow-up from Microsoft on its July change, the timing of Davies's confirmation, and whether the Senate hearings ask vendors how they test and roll out patches.