NSA’s Classified Network Restored After Three-Day Outage Linked to Software Patch
The National Security Agency’s classified communications network, NSANet, appears to be mostly restored after a three-day outage caused by patching efforts in PHP software. The disruption forced staggered work schedules and delayed openings at the agency’s Maryland headquarters. The outage did not affect intelligence-gathering capabilities, according to a former NSA technology official, and the agency is now operating under normal conditions with minor exceptions.
In November 2026, the National Security Agency’s classified communications network, NSANet, experienced a three-day outage that disrupted operations at its Maryland headquarters and its Georgia campus, a key node for Middle East intelligence. The disruption, which began around November 17 and was largely resolved by November 20, forced staggered work schedules and delayed openings under “Code Orange” conditions, though essential personnel were required to report as scheduled. The outage was traced to patching efforts in PHP, a widely used open-source scripting language, following the discovery of major vulnerabilities in the software the previous month. According to Director of National Intelligence Jay Clayton, the issue stemmed from these patching activities, though the NSA confirmed it did not affect the agency’s intelligence-gathering capabilities. The incident echoes past disruptions, such as a 2000 crash that halted intelligence processing for three days and a 2013 website outage attributed to a scheduled update. Despite the severity of the disruption, the agency reported it is now operating under normal conditions with minor exceptions. The incident highlights the risks of widespread software dependencies in critical infrastructure, even when patches are intended to improve security.
The outage underscores the fragility of critical national security systems amid increasing reliance on shared software infrastructure. While the NSA’s intelligence collection remained intact, the disruption to internal communications could have delayed decision-making during a high-risk period, potentially affecting operational readiness. The incident adds to a growing list of high-profile tech failures—including FAA groundings, Microsoft outages, and banking disruptions—suggesting systemic vulnerabilities in how organizations manage updates and patches. The reliance on widely used open-source software like PHP, while cost-effective and flexible, introduces cascading risks when flaws are exploited or patched improperly. Comparable cases, such as the 2017 WannaCry ransomware attack that exploited unpatched systems globally, show how a single vulnerability can ripple across sectors. What remains uncertain is whether the NSA’s response will prompt broader reforms in federal cybersecurity practices, particularly around testing and deployment of patches in mission-critical systems. The coming months may reveal whether this event leads to enhanced oversight or deeper integration of resilience testing in national security technology frameworks.