Get a free audit
Apple credit Apple credits the researcher who runs our AI penetration testing.

Field Notes / Outage

Routine maintenance took down the NSA’s classified network. Your next patch night can do the same.

On 17 November the network the NSA uses to share classified information went offline during scheduled maintenance. The Director of National Intelligence says a security patch caused it, and officials see no sign of an attack. The lesson for every business is about patching: attackers now move within hours of a fix, so you have to patch fast and still keep a way back.

Author
Red Team Partners
Read
5 MIN READ
Filed
18 Nov 2026
Server racks lit red in a dark, misty data centre.

Update, 18 Nov: the Director of National Intelligence says a security patch caused the outage. The NSA closed its campus to most staff on Tuesday night, and restoration was not confirmed complete CNN .

The network the National Security Agency uses to store and share classified information went offline on Tuesday 17 November, during what the agency called “scheduled routine maintenance” CBS News . Officials say they see no evidence of a cyberattack. Director of National Intelligence Jay Clayton said the agency had been patching major vulnerabilities found last month, and “some of these systems” did not come back up as expected CNN . If the best-funded intelligence agency in the world can lose its own network to a patch night, so can you.

What is confirmed, and what is not

QuestionWhat the reports say
What went downNSA Net, the agency’s internal network for classified communications. One source said it was “not completely shut down” but gave only intermittent service The Record .
Official cause“Temporary degradation during scheduled routine maintenance”, in the NSA’s words CBS News . Jay Clayton, Director of National Intelligence, on Fox Business: “The patching that has gone on following that has caused some of these systems to not come back up when you patch them as expected. That is what has happened at the NSA today.” CNN
Which patchClayton spoke of major vulnerabilities discovered last month. According to CNN, those are the PHP flaws that AI tools helped researchers exploit and that the NSA itself urged organisations to patch CNN . CNN names no CVE and nobody has confirmed which update the NSA applied. Background: our PHP2Shell note on the PHP flaws patched in October.
Cyberattack?No evidence, according to two US officials, a White House spokesperson UPI and Clayton CNN .
Effect on staffStaggered arrivals at Fort Meade, so tens of thousands of people did not all log on at once The Record . Some work moved to other NSA sites. On Tuesday evening staff were told to report as scheduled; later that night the campus closed to all but essential personnel until further notice CNN .
HistoryOne source said the network had been unstable for weeks The Record .
Not knownWhen it started, the exact patch, how many people lost access, and whether full service is back. A source told CNN restoration was ongoing but not complete.

Four outages in six days, all blamed on change

The NSA was the fourth large US system to fall over in under a week. Line up what each organisation has said and the same word keeps coming back.

OutageStated cause so far
Microsoft 365, 12 NovMicrosoft rolled back a recent configuration change and said it was not aware of malicious activity (our note). A senior official later blamed a months-old bug The Record .
FAA ground stop, 13 NovNo evidence of a cyberattack. The FBI is reportedly looking at a software update, and CBS reported the outage followed an update to the air traffic communications network. No official root cause yet SecurityWeek .
Chase and other banks, 16 Nov“A software bug in on-premise hardware system”, in Chase’s words, and not “cyber-related” NBC News .
NSA Net, 17 NovA software patch for vulnerabilities found last month, according to the Director of National Intelligence CNN .

Four different operators, four different systems, and every one of them appears to have hurt itself with an update, a configuration change or a maintenance job. The US Homeland Security Secretary said it appeared the FAA had been applying patches and new equipment that was “overwhelming the older system” SecurityWeek .

When the first explanation changes

Officials say maintenance, and we have no reason to say otherwise. First statements get written in the first hours, with very little information, and they have been revised before.

In 2015 the US Office of Personnel Management said personnel files on 4.2 million people had been exposed. A month later it announced a second, related breach of its background-check records, covering 21.5 million people Nextgov . The first number was true. It was also nowhere near the whole story.

Companies do not get to stay vague for ever. A US-listed company has to file a Form 8-K within four business days of deciding a cyber incident is material Cooley , and a US bank has to tell its regulator within 36 hours of deciding a serious incident has happened OCC . The bank rule covers plain hardware and software failures as well as attacks.

For your business the lesson is the same either way. Control your changes, keep a way back, keep a way to talk that does not run on the broken network, and expect scammers to pose as the fix.

Patches break things, even at Fort Meade

This is not the NSA’s first bad maintenance window. In 2013 its public website went dark and officials blamed a scheduled update. In 2000 the agency’s computers went down for three days, and the recovery reportedly cost $1.5 million The Record .

Chris Krebs, the former head of CISA, put the wider point plainly on CNN. Teams are patching “at a rate far beyond anything in the past”, he said, and every patch or update can destabilise the system it lands on Deadline .

That matches what we see. Patch volume is up, and most change processes were written for a world with a monthly patch day.

Patch fast and patch safely: both have to be true

You cannot slow down any more. Yesterday we wrote about an attacker tool that reads a security patch and writes the exploit by itself. The FBI warned on 13 November that some attackers using an AI-driven framework went from first contact to privileged access in under three hours Fox News . And the N-central flaw was being exploited about five hours after the code went public.

So you cannot wait a month to see whether a patch is stable. You also cannot push every update to every server at 9 a.m. and hope.

What kept the NSA working, and your version of it

The NSA says its mission-critical systems kept running and backup centres picked up the work CBS News . Strip away the classified part and every measure has a small-business equivalent.

What the NSA didYour version
Kept critical systems apart from the restPatch your payment, email and remote-access systems in a separate window from everything else, so one bad update cannot take all three.
Moved work to backup sitesKnow which work can run from another site, a cloud tenant or a laptop with offline copies, and test it once a quarter.
Staggered staff arrivalsRoll updates out in rings: IT first, then one team, then everyone. A failure hits ten people instead of two hundred.
Kept talking to leadership on other networksAgree a channel outside your main network, such as a phone tree or a messaging group on personal phones, and say in writing that staff will never be asked for passwords or payments on it.

That last row matters for security as much as uptime. A business in the middle of an outage is easy to fool, which is why scammers used the US bank outage as their opening line and why the Microsoft 365 outage left email filtering exposed.

Test the way back before you need it

If nobody has ever run your rollback plan, it is a guess. In a red team engagement we look at the change process as an attacker would: who can push an update, whether a bad one would be noticed, and whether your fallback channel can be spoofed. A penetration test after a big change tells you the patch closed the hole it was meant to close. So, one question for your next patch night: if your main network went down at 8.30 tomorrow morning, which channel would your team use to say so, and would they trust a message on it from someone they had never heard from?

Questions readers ask

Was the NSA network outage on 17 November 2026 a cyberattack?

Officials say there is no evidence of one. Two US officials told CBS News there was no sign of a cyberattack, and a White House spokesperson said the same. The NSA described a “temporary degradation during scheduled routine maintenance”, and Director of National Intelligence Jay Clayton said it followed a software patch for major vulnerabilities found the month before. Clayton also said there is no sign that any of the week’s outages was a cyberattack.

Is NSA Net back online?

Not confirmed. On Tuesday evening 17 November NSA staff were told to report to work as scheduled, but later that night the agency closed its campus to most employees and kept only essential personnel while it restored the network, CNN reported. A source told CNN restoration was ongoing but not complete. The NSA says mission-critical capabilities stayed operational throughout.

Were the Microsoft, FAA, bank and NSA outages connected?

No report we read links them, and officials say none of the four was a cyberattack. Each was blamed on a change or a fault inside the organisation: a configuration change and a bug at Microsoft, a network update the FBI is reportedly examining at the FAA, a software bug at Chase, and routine maintenance and patching at the NSA. Final root causes for the FAA and NSA had not been published.

What should a business learn from the NSA outage?

A patch can take down a network as surely as an attacker can. Test patches on a small group of systems first, write the rollback steps before you start, roll out in stages, and keep a way to talk to your team that does not run on the network you are changing. Attackers now exploit fresh patches within hours, so keep patching fast and make it safer.

References

Sources

  1. CBS News. “NSA’s classified internal network goes down, sources say.” Updated 17 November 2026, 2:40 pm EST. cbsnews.com
  2. Recorded Future News. “NSA Net, agency’s classified internal network, faces unspecified disruptions.” The Record, 17 November 2026. therecord.media
  3. UPI. “Reports: Highly classified National Security Agency network goes down.” Via Yahoo News, 17 November 2026. yahoo.com
  4. Deadline. “Another Day, Another Outage: As CNN Reports On NSA Network Down, News Outlets Seize On Back-To-Back Incidents Of Cyber Chaos.” 17 November 2026. deadline.com
  5. Fox News. “NSA’s highly classified communications network disrupted by widespread outage.” 17 November 2026. foxnews.com
  6. Kovacs, E. “No Signs of Hacking in FAA Ground Stop as FBI Reportedly Probes Software Update.” SecurityWeek, November 2026. securityweek.com
  7. Wile, R. and Steinberg, K. “Chase says transactions back to normal after outage online and at some branches.” NBC News, 16 November 2026. nbcnews.com
  8. Nextgov. “OPM: 21.5M impacted by background-check breach.” 9 July 2015. nextgov.com
  9. Cooley. “SEC Adopts Comprehensive Cybersecurity Disclosure Requirements.” 2 August 2023. cooley.com
  10. Office of the Comptroller of the Currency. “Computer-Security Incident Notification: Final Rule.” Bulletin 2021-55, 23 November 2021. occ.gov
  11. CNN. “Highly classified US national security communications network goes down, sources say.” 17 November 2026, updated. edition.cnn.com