The National Security Agency’s classified internal network stayed down for three straight days this week, forcing staff at Fort Meade to work staggered shifts even after officials said the system was fixed.
Story Snapshot
- The NSA’s classified network, known as NSA Net, went down starting November 17, 2026, and disruptions lasted into a third day.
- The agency called it a “temporary degradation during scheduled routine maintenance” and said mission-critical work kept running.
- Two U.S. officials said there was no evidence of a cyberattack, and sources pointed to patching tied to critical PHP software flaws.
- The outage hit alongside a string of other tech failures at airlines, banks, and Microsoft, fueling public worry even though officials call them unrelated.
Network Failure Drags Into Third Day
The National Security Agency’s classified internal network first showed problems on November 17, 2026. An agency spokesperson told CBS News the disruption was a “temporary degradation during scheduled routine maintenance”. The statement said some internal systems were affected, but added that mission-critical capabilities remained fully operational and the agency’s ability to defend national security continued without interruption.
Fort Meade responded by staggering employee arrival times to ease pressure on the recovering systems. That arrangement reportedly continued even after NSA Net came back online, because officials worried about too many people logging in at once. The agency did not say exactly how many systems were affected or give a full timeline for when normal operations fully returned.
Officials Say No Sign Of An Attack
Two U.S. officials told CBS News that, at this point, there is no evidence the disruption was caused by a cyberattack. Separately, sources familiar with the situation said the outage resulted from routine system patching, though the exact circumstances were not fully explained. The agency’s networks are built with multiple layers of backup systems meant to keep operations running during planned maintenance or unexpected problems.
A day later, Director of National Intelligence Jay Clayton addressed the outage during a congressional proceeding on November 18. “These are separate service outages associated with maintenance and technical changes,” Clayton said. “They are not a coordinated or state-sponsored attack”. Another official, identified as Raia, said there was “no indication whatsoever” of cyber malicious activity tied to any of the recent incidents.
Patching Tied To Software Vulnerabilities
CBS News later reported the outage was linked by multiple sources to urgent patching after critical vulnerabilities were found in PHP, a common web programming language. Clayton gave more detail on Fox Business, saying the patching process itself caused some systems to fail. “That is what has happened at the NSA today,” he said, describing systems that did not come back up as expected after being patched.
That account differs somewhat from the agency’s first description of “scheduled routine maintenance.” The public explanation has not fully clarified whether workers were doing planned upkeep or scrambling to fix an urgent security gap. Either way, officials have consistently said the problem came from inside the system, not from an outside intruder.
Part Of A Wider Pattern Of Outages
The NSA’s trouble came during a stretch of unrelated technology failures hitting airlines, banks, and Microsoft services. That timing made some of the public suspect a coordinated attack, even though officials have repeatedly said the incidents are separate. Cybersecurity researchers note that figuring out whether an outage was caused by an attacker or by a technical mistake often takes real time, and early statements usually reflect the best current understanding rather than a finished investigation.
Government auditors have also flagged a bigger, ongoing problem across federal agencies: old computer systems. A Government Accountability Office review found that many federal IT systems rely on outdated software and hardware, some of it decades old, with known security gaps that are hard to fix quickly. That broader pattern helps explain why patching work, even routine patching, can cause real disruptions when it goes wrong.
Why This Still Matters
For an agency built around guarding the nation’s most sensitive information, three days of network trouble is not a small event. Officials say the explanation is mundane: maintenance and patching, not an attack. But the fact that a core system meant to run with heavy backups still went dark for days raises fair questions about how resilient these systems really are, regardless of the cause.
Classified US national security communications network hit by outage, NSA says https://t.co/2kJgXA0RRX
— Veterans United March (@VetsUnitedMarch) November 20, 2026
No official has released a detailed public account of what exactly failed, when it failed, or why the fix took as long as it did. Americans across the political spectrum who already worry about government competence are likely to notice that gap, even as they take officials at their word that this was not an attack.
Sources:
© libertysociety.com 2026. All rights reserved.














