NSA NSANet maintenance outage

Officials attributed the internal network disruption to patching; the agency confirmed recovery on November 20.

Last modified

Summary

  • Environment: NSA NSANet internal communications network
  • Operational impact: Several days of disruption and temporary workforce access restrictions.
  • Financial impact: No verified financial-loss total has been disclosed.
  • Record status: Developing record. Reviewed November 22, 2026; updated as evidence emerges.

What happened

The National Security Agency confirmed normal operating conditions on November 20 after several days of internal-network disruption, according to The Record. [1]

Impact

The disruption affected NSANet, used for internal classified communications. A morning workforce message still described exceptions and delayed openings at some facilities; the later spokesperson statement confirmed normal conditions. [1]

Timeline

  1. Normal conditions confirmed

    The agency’s confirmation followed the morning’s remaining restrictions.

    [1]
  2. Briefing updated

    This briefing was last reviewed and updated on November 22, 2026.

Threat Group & Attack Vector

DNI Jay Clayton attributed restart failures to patching; reporting connected the maintenance to PHP. Officials said the disruption was not a cyberattack. A detailed technical postmortem was not available in the reviewed evidence. [1]

Actors

  • No threat actor is attributed to this operational outage.

TTPs

  • No MITRE ATT&CK technique is mapped to this maintenance-related outage.

Response

NSA confirmed recovery, but the exact onset and recovery measures remain undocumented publicly in the reviewed report. [1]