NSA classified network outage resolved after nearly four days

RUKUS· · 36h ← 5d
Go Rogue

The NSA's classified internal network, NSANet, went down on November 17 during scheduled maintenance, locking most employees out of the agency's classified email system.

The outage also struck NSA Georgia, a Fort Gordon hub supporting Middle East intelligence, though officials said the most sensitive intelligence-gathering systems kept working.

Officials said the failure was not a cyberattack but stemmed from urgent patching of vulnerabilities in PHP, some of which AI tools helped discover.

Patching went slower than expected, and employees returned on staggered schedules until the outage was declared resolved on November 20.

The NSA failure came amid a week of US outages at Microsoft, airlines, banks and Apple that officials also blamed on upgrades, not attacks.

NSANet is essentially a giant classified email system; a 2024 Maryland state document put NSA employment at about 39,000 people.

  1. NSANet, the NSA's highly classified internal communications network for sharing classified information, went down on November 17.

    Sources said there was no evidence of a cyberattack behind the NSANet outage.

    The NSA staggered personnel arrivals at its Fort Meade, Maryland headquarters while it worked to determine the scope of the outage.

    Homeland Security Secretary Markwayne Mullin said in a CNBC interview, "I can tell you with complete certainty that we are not under attack; there's no cyber threat that's taken place."

  2. The NSA attributed the outage to temporary degradation during scheduled routine maintenance and said mission-critical capabilities remained fully operational.

    The NSA said in a statement, "While some internal systems were affected, mission-critical capabilities remain fully operational and our ability to defend national security continues."

  3. An NSA employee information line described a code yellow, the second-highest alert level, and told non-emergency staff not to report before noon on November 17.

    The outage appeared to be caused by a need to patch software with a system update, though it was not clear what software was at issue.

    NSANet had been unstable for weeks before the outage, fueling frustration among the NSA workforce.

  4. Chris Krebs said how quickly authorities can rule out a cyberattack depends on how long anomalous activity has been detected across the network.

  5. Director of National Intelligence Jay Clayton said systems being upgraded are "not coming back as expected in all cases," calling the episode an upgrade in patching rather than a cyber attack.

  6. Secretary of State Marco Rubio said there was "zero" information that the outages were related to each other or caused by a malign actor.

    President Donald Trump played down the disruptions, saying "things like that happen" and "It's fine."

    Karoline Leavitt, Trump's former press secretary, said on Fox News that "transparency is key" and urged the White House to explain what it knows.

    Tricia McLaughlin, a former Homeland Security spokesperson, posted, "Americans aren't stupid. We want and deserve to know what's really going on."

    Meghan McCain wrote on X that "someone high in the administration needs to get on tv and tell the American people NOW what is going on."

    Laura Loomer wrote on social media, "Our leaders are lying to us. This is very clearly a coordinated cyber attack."

    Director of National Intelligence Jay Clayton said, "Looking very diligently across the landscape, we are not seeing this as a cyber attack incident."

  7. A senior administration official said patching to restore access to the NSA's classified network was going slower than expected.

    The NSA closed its Fort Meade campus to most employees on Tuesday night, reverting to essential personnel only while it worked to restore the network.

    A senior administration official said the week's outages were not a cyberattack, were not connected to any actor, and involved no state sponsorship.

  8. A Breaking Points host said the outages caused or contributed to a stock market rout in which the Dow shed nearly 1,000 points.

    A Breaking Points host said patches were being uploaded almost immediately without testing, which he said was what made sites stop working at Microsoft, the NSA, and Chase.

    Senator Josh Hawley said of the outages, "if it is all a coincidence, it is like the greatest coincidence in the history of the world."

    Vice President JD Vance said the government does not see a crisis coming and that much of what was being reported was basic good government to keep the military prepared.

  9. Two sources said NSANet was back up and running on November 18, but the NSA kept a staggered arrival schedule, known as Code Gray, fearing too many simultaneous logons.

    Director of National Intelligence Jay Clayton linked the NSA outage to urgent software updates following the discovery of critical PHP vulnerabilities.

  10. The disruption hit NSA Georgia at Fort Gordon in Augusta, Georgia, which supports signals intelligence and cyber operations focused on the Middle East.

    NSA Georgia personnel could not use NSANet to communicate with colleagues deployed in the Middle East but used backups and workarounds to share information.

    Officials said the NSA's most sensitive and important intelligence-gathering systems functioned throughout the outage.

    Officials briefed on the outage said it was not a cyberattack but appeared tied to the NSA's handling of software updates for vulnerabilities in PHP.

    Private researchers disclosed the PHP vulnerabilities in the month before the outage, and AI tools helped discover them.

    Director of National Intelligence Jay Clayton told the House Homeland Security Committee he had a very high level of confidence that none of the downed systems resulted from a cyberattack.

    Senator Mark Warner, Democratic vice chairman of the Senate Intelligence Committee, said AI now identifies vulnerabilities across enormous numbers of systems at unprecedented speed, putting tremendous strain on systems not built for that pace of change.

  11. The classified network was still down on November 19, a third day, with nonessential NSA staff told to check with supervisors and otherwise work from home.

  12. The NSA declared the NSANet outage resolved on November 20, telling employees to return on staggered schedules, with most staff expected back by midday Friday.

    The NSA's employee voicemail line announced on November 20 that the agency was operating under normal conditions with exceptions.

    On several occasions during the outage, employees told to report to work on a staggered basis returned home without ever logging in.

    Current and former officials said an NSANet outage lasting almost four days was unusually long and disruptive for the agency.

Sign in with subscription

Free during the beta.

Clear all notifications?

Your bells stay on. Only this list empties.