The facts
A defense official identified the affected network as NSANet to AP. CBS and CNN also reported the interruption, citing people familiar with it. [1][2][3]
CBS reported staggered arrivals at the Maryland headquarters and that some activities shifted to other agency facilities. [1]
The agency said the disruption was temporary degradation during routine maintenance; officials said mission-critical capabilities continued, and CNN reported Five Eyes sharing was unaffected. [2][3]
On Nov. 18, Recorded Future News cited a source saying NSA Net was working but intermittent interruptions and a burdensome login process continued. The source said staff scheduling remained staggered and speculated full restoration could take another day or two; the NSA did not respond. [4]
Recorded Future News reported that Director of National Intelligence Jay Clayton told lawmakers the recent outages were separate service problems associated with maintenance and technical changes, not a coordinated or state-sponsored attack. [4]
AP separately reports Secretary of State Marco Rubio said there was no evidence the outages were linked or caused by a malign actor. This is a government-wide assessment, not a restoration update for NSA Net. [5]
CBS reported Nov. 18 that two sources familiar with NSA Net said it was back up and running. The NSA had not publicly confirmed full restoration in CBS’s report; staggered arrivals continued because of login-load concerns. [4][7]
CNN reported that NSA Georgia personnel supporting Middle East-focused signals-intelligence and cyber operations could not use NSANet to communicate with regional colleagues; backup channels or workarounds allowed information to be shared. This is source-reported operational friction, not evidence that mission-critical work stopped. [6]
CNN reported some nonessential Maryland staff were told not to report on Nov. 18 while patching continued. CBS later cited two sources saying NSA Net was back up, but did not establish when staggered arrivals ended. [6][7]
CBS reported that NSA Net was back up and running, citing two sources familiar with the system; staggered arrivals continued because of concern about simultaneous logins. [7]
DNI Jay Clayton told Fox Business that patching after critical PHP vulnerabilities had caused some systems not to come back up as expected. CBS linked the NSA outage to urgent PHP patching; this is an attributed explanation, not a published NSA technical incident report. [7]
CBS reported NSA said mission-critical information sharing had not been impacted and staff were asked to delay nonessential tasks. The agency did not respond to CBS’s request for a further update on Wednesday. [7]
AP reported Nov. 19 that NSA Net went offline during scheduled maintenance and quoted DNI Jay Clayton on PHP patching; the report did not provide a new status on stable restoration. [8]
CNN reported Nov. 19 that the outage had entered a third day and that patch restoration was slower than expected. Some nonessential Maryland staff had been told not to report, and Georgia personnel could not use NSA Net to reach regional colleagues; workarounds kept information sharing going. [10]
CNN’s Nov. 19 report conflicts with CBS’s Nov. 18 account citing two sources who said NSA Net was back up. AP’s Nov. 19 account describes the outage beginning during scheduled maintenance but gives no later restoration confirmation. [9][7][8]
The NSA said mission-critical capabilities remained operational. The opened reporting does not establish a broad intelligence-sharing failure, an interruption to critical operations, or a cyberattack. [2][3]
CNN’s Nov. 19 report conflicts with CBS sources’ Nov. 18 account that NSA Net was back up. The NSA has not publicly confirmed stable full restoration, and no broad mission-critical failure or cyberattack is established. [10][7][8][2][3]
NBC reported NSA Net remained down Thursday Nov. 19, with nonessential staff home for a third day. Its sources said intelligence collection and cybersecurity oversight were unaffected and a Georgia work site handling Middle East intelligence was affected. [11]
NSA’s Nov. 17 statement describes temporary maintenance degradation and says mission-critical capabilities remained operational. [12]
CBS sources’ Nov. 18 restoration account conflicted with CNN and NBC reports that the outage continued on Nov. 19. A later Nov. 20 employee voicemail and CNN source described NSANet as restored with staggered arrivals still in effect; The Record said some facilities remained under Code Orange. The agency says mission-critical functions continued. [11][12][7][10][13][14]
Still unconfirmed
- Which facilities remained under Code Orange or delayed openings and when those exceptions ended.
- Whether Washington and other NSA sites maintained stable access after the Nov. 20 voicemail and whether staff returned to regular schedules.
- Whether the NSA will publish a technical account of the maintenance, PHP patching and recovery.
Corrections & updates
Substantive status update, Nov. 18 UTC: added a second-day report that NSA Net was working but intermittent interruptions and login strain continued. The one-to-two-day restoration estimate is attributed to an unnamed source; the NSA did not confirm it. Added the DNI’s public assessment that recent outages were separate maintenance or technical events, not a coordinated or state-sponsored attack.
Substantive update, 19 November UTC: added CNN’s Nov. 18 reporting that staff at a Georgia intelligence hub could not use NSA Net to reach regional colleagues but used backup channels, and that some nonessential Maryland staff were told not to report while patching continued. The report does not establish a mission-critical outage or confirm full restoration.
Substantive status update: CBS reported Nov. 18 that two sources familiar with NSA Net said it was back up and running, although staggered arrivals continued. The PHP-patching explanation is attributed to CBS sources and DNI Jay Clayton; the NSA did not respond to CBS’s follow-up request. Mission-critical service is not described as interrupted.
Substantive update, Nov. 19 UTC: added AP’s report that the outage began during scheduled maintenance and its account of DNI Jay Clayton’s PHP-patching explanation; AP gives no stable-restoration update. Kept this distinct from CBS’s Nov. 18 source-reported return to service and the NSA’s statement that mission-critical capabilities remained operational.
Substantive status update, Nov. 19 UTC: added CNN’s report that NSA Net disruption persisted into a second day and affected some Maryland schedules and Georgia communications, with backup channels used. This conflicts with CBS sources’ reported return to service; AP gives no stable-restoration update. The NSA said mission-critical capabilities continued.
Substantive status update, 19 November UTC: CNN’s Nov. 19 report says NSA Net disruption had entered a third day and patch restoration was slower than expected. Some Maryland staff were told not to report and Georgia staff could not use the normal channel, while backup routes kept information sharing going. This conflicts with CBS sources’ Nov. 18 restoration account; the NSA said mission-critical capabilities remained operational, and stable full recovery is unresolved.
Status update, 20 November UTC: added NBC’s Nov. 19 third-day report and NSA’s direct statement. NBC sources say collection and cyber oversight continued; CBS’s Nov. 18 reported restoration conflicts with CNN/NBC. Stable full restoration remains unconfirmed.
Substantive status update, Nov. 20 UTC: a later employee voicemail and CNN source report describe NSANet as restored and Washington as operating under normal conditions with exceptions. The Record reports some facilities still under Code Orange with delayed openings. These later reports supersede the earlier-week uncertainty about whether the network remained down; residual access and schedule exceptions and a detailed agency account remain unresolved.
Sources
References support the numbered facts above. Source checks: 20 Nov 2026, 18:12 UTC.
The Record and CNN report Nov. 20 workforce voicemail language and the restoration status; CNN also cites a source familiar with the matter. The Record says NSA Georgia intelligence operations and support for the Asia trip were not negatively affected, citing two sources. The NSA did not immediately respond to The Record. Earlier CBS/CNN/NBC reports about the outage are kept as historical, time-specific accounts; they do not override the later Nov. 20 restoration update.
- NSA’s classified internal network goes down, sources say
CBS News · Reporting · 17 Nov 2026
- Classified communications network at the National Security Agency goes down, defense official says
The Associated Press · Reporting · 17 Nov 2026
- Highly classified US national security communications network goes down, sources say
CNN via KTVZ · Reporting · 17 Nov 2026
- NSA continues response to interruptions in classified internal network
The Record from Recorded Future News · Reporting · 18 Nov 2026
Current restoration status relies on an unnamed source; the agency did not respond.
- Rubio says there’s ‘zero’ information that US outages are linked or caused by a malign actor
The Associated Press · Reporting · 18 Nov 2026
Reports the DNI’s assessment to lawmakers and keeps the separate outages distinct.
- NSA outage disrupts key intel hub that supports Middle East intelligence and operations, sources say
CNN Newsource via KESQ · Reporting · 18 Nov 2026
CNN cites unnamed sources for effects at an NSA Georgia operations hub and Maryland headquarters. It reports backup channels were used, some nonessential day-shift staff were told not to report on Nov. 18, patching took longer than expected, and mission-critical systems continued. It does not establish a cyberattack or a public full-restoration time.
- National Security Agency network outage linked to software vulnerability
CBS News · Reporting · 18 Nov 2026
Opened CBS News’ Nov. 18 report. It cites two sources saying NSA Net was back up and running, reports staggered arrivals continued, and attributes the PHP-patching explanation to multiple sources and DNI Jay Clayton. The NSA had not responded to a follow-up request.
- National Security Agency network outage during scheduled maintenance
The Associated Press · Reporting · 19 Nov 2026
AP reports the network went offline during scheduled maintenance and quotes DNI Jay Clayton on PHP patching. The article gives no new current status for stable NSA Net restoration.
- NSA communications outage stretches into second day, sources say
CNN via AOL · Reporting · 19 Nov 2026
CNN’s Nov. 19 report says the outage continued into a second day, with nonessential Maryland personnel asked to stay home and Georgia personnel unable to use the network to reach regional colleagues; backup channels were available. This conflicts with CBS sources’ Nov. 18 report that the network was back up.
- NSA outage disrupts key intel hub that supports Middle East intelligence and operations, sources say
CNN Newsource via KESQ · Reporting · 19 Nov 2026
CNN reports Nov. 19 that the outage entered a third day and restoration was slower than expected. It describes impaired normal communications at the Georgia hub and backup channels; the NSA’s statement that mission-critical capabilities continued remains distinct from stable full restoration.
- Classified NSA network is still down, leaving some staff working from home
NBC News via NBC Bay Area · Reporting · 19 Nov 2026
NBC reports the network remained down Thursday, with nonessential staff home for a third day; two sources said collection and cyber oversight were unaffected and a Georgia Middle East-intelligence site was affected. This conflicts with CBS’s Nov. 18 restoration account.
- NSA statement on network issues
National Security Agency · Primary source · 17 Nov 2026
NSA says some internal systems were temporarily degraded during scheduled maintenance while mission-critical capabilities remained operational with redundancy.
- NSA resumes normal operations following internal network disruptions
The Record · Reporting · 20 Nov 2026
- Outage at NSA’s highly classified communications network has been resolved, sources say
CNN via KRDO · Reporting · 20 Nov 2026