Reference · public sources
← Incidents

Incident reportDisputed / suspected cyberattackReport version 1 · November 21, 2026

NSA classified network (NSANet) outage

The National Security Agency's classified internal network, NSANet, went down on November 17 and some staff were asked to delay reporting to Fort Meade. Stated cause: officials linked the outage to applying a software patch for major vulnerabilities; the NSA called it a temporary degradation during scheduled maintenance. Multiple US officials said it was not believed to be a cyberattack. Restoration after nearly four days is reported by a single source.

DisputedAttribution: Not attributedReference data · public sources

01Executive assessment

  • DisputedNSANet was down from at least early Tuesday morning; some staff were asked to delay arriving at Fort Meade. [1]
  • DisputedStaff received a 'code yellow' notice governing whether to report to Fort Meade. [2]
  • DisputedStated cause: the outage resulted from applying a software patch for major vulnerabilities. [3]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

The National Security Agency's classified internal network, NSANet, went down on November 17 and some staff were asked to delay reporting to Fort Meade. Stated cause: officials linked the outage to applying a software patch for major vulnerabilities; the NSA called it a temporary degradation during scheduled maintenance. Multiple US officials said it was not believed to be a cyberattack. Restoration after nearly four days is reported by a single source.

Incident type
Disputed / suspected cyberattack
Event period
November 17, 2026 to November 20, 2026
Date precision
day
Evidence basis
Outage confirmed by multiple outlets; officials state a non-cyber cause (software patch / maintenance)
Sectors
Government, Defense

Start as reported by Bloomberg and CNN; restoration date from a single source (NewsBytes).

03Evidence chronology

Publication dateDevelopmentTypeSource
November 17, 2026Bloomberg and CNN report NSANet down; staff told to delay arrival.News report[1]
November 18, 2026Officials link the outage to a software patch; no cyberattack suspected.Official statement (reported)[3]
November 20, 2026Network reported restored after nearly four days.News report[5]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
National Security Agency (NSA)Affected organization (outage)Fort Meade, Maryland, United Statessite · Organization headquarters named in the reporting

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Attributed actor
Not attributed
Assessed by
No assessment
Confidence
unknown
Sources

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

No incident-specific procedure evidence has been recorded yet.

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESBloombergNovember 17, 2026CNNNovember 17, 2026CBS NewsNovember 18, 2026WPDE (Sinclair)November 18, 2026NewsBytesNovember 20, 2026National Security Agenc…

07Software and indicators

No publicly shareable indicators are recorded for this incident.

08Business exposure and priorities

Organizations in government, defense should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

09Defensive actions

No actor-level defensive guidance is linked.

From the dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]NSA Faces Outage of Classified Network, Disrupting Internal OperationsBloomberg · published November 17, 2026 · collected November 21, 2026
  2. [2]Highly classified US national security communications network goes down, sources sayCNN · published November 17, 2026 · collected November 21, 2026
  3. [3]National Security Agency network outage linked to software vulnerabilityCBS News · published November 18, 2026 · collected November 21, 2026
  4. [4]NSA says classified network experienced temporary disruption during routine maintenanceWPDE (Sinclair) · published November 18, 2026 · collected November 21, 2026
  5. [5]NSA's NSANet restored after nearly 4-day outage at Fort MeadeNewsBytes · published November 20, 2026 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.