# CNN said resolved, the Post said restored, Fox said patched; every duration in the corpus is a rounding with a masthead attached, and the PHP-patching cause stays hedged everywhere except where Fox Business narrates Clayton's link and where Clayton is quoted directly.

- Canonical: https://thestochasticparrot.com/audits/nsa-net-outage-restored
- Structured (spans, splits, sources): https://thestochasticparrot.com/audits/nsa-net-outage-restored.json
- Date: 2026-11-20T20:27:30Z
- Context: A coverage brief: how 16 outlets each framed the same news event.
- License: CC BY 4.0

---

[ COVERAGE BRIEF // nsa-net-outage-restored // 2026-11-20 ]

# NSA Net Restored After Nearly Four-Day Outage, Depending on Who's Counting

## CNN reported the NSA network resolved, the Post reported it restored and Fox News reported it patched; the durations those files print differ by outlet, and the PHP-patching cause stays hedged except where Fox Business narrates Clayton's link and where Clayton is quoted directly.

The desk was here Tuesday, when the network went down and the story was a source count moving between outlets. This is the second entry in that ledger: the network came back, and what the corpus offers on Friday is an arithmetic of rounding. One stretch of clock — Tuesday to Friday — is measured four ways in the corpus, each measurement stapled to the outlet that produced it.

The restoration itself is reported, not announced. Three files carry it, each with its own phrasing and its own source:

── SHARED: restoration_reported · three_restatements_three_sources ──
CNN: "The outage of a key internal communications network at the National Security Agency that has kept large swaths of employees locked out for more than three days has now been resolved, according to a source familiar with the matter and a voicemail inbox recording for employees at the main headquarters in Maryland."
New York Post: "The National Security Agency's highly classified internal communications network has been restored after nearly four days of disruptions that left scores of employees unable to log in, sources and officials said."
Fox News: "An outage that was affecting the National Security Agency's internal classified communications network has been patched and all employees are returning to work by this afternoon, a source familiar with the matter told Fox News on Friday."

Resolved, restored, patched. CNN's resolution rests on a source plus a voicemail inbox recording; the Post's restoration on "sources and officials"; Fox's patch on one source familiar with the matter. A fourth file, CBS News, had the network up on Thursday — that exhibit below. No file states an end time. The desk will not turn "resolved," "restored" or "patched" into an end time.

Now the arithmetic. The same outage, as each newsroom counted it:

── NAMING: duration_counts · four_roundings_of_one_stretch ──
CNN: "that has kept large swaths of employees locked out for more than three days has now been resolved"
CNN: "But the length of the outage — almost four days — was unusually long and disruptive, current and former officials said."
New York Post: "has been restored after nearly four days of disruptions"
NBC News: "resulting in some employees being ordered to work from home for a third day in a row, according to two people with knowledge of the matter."

CNN's own file carries two counts: the lede says "more than three days," and a later sentence says "almost four days" — both true at different moments of the same report, the way a race's length depends on when you check the stopwatch. The Post rounds to "nearly four." NBC, writing Thursday, counts "a third day in a row." Four counts are printed above; none is corrected to match another, and no fifth figure is supplied.

Thursday is where the corpus pulls two directions, and the corpus does not time-align the pulling:

── FRAMING: thursday_status · back_up_vs_remained_down ──
CBS News: "According to two sources familiar with the system, NSA Net as of right now is back up and running."
NBC News: "An internal classified computer network used by the National Security Agency remained down on Thursday, resulting in some employees being ordered to work from home for a third day in a row, according to two people with knowledge of the matter."

Both filed Thursday. CBS anchors its status to "as of right now"; NBC's file carries no hour. Whether the two reports describe different hours of the same afternoon or different states of the same network is not settled by these records; neither account is corrected here, and neither set of unnamed sources is preferred over the other.

The staffing protocol has two printed names, and the files do not establish they name the same thing:

── NAMING: staffing_protocol · code_gray_vs_code_yellow ──
CBS News: "There is no word yet on how long the agency will continue the staggered arrival schedule, known as "Code Gray.""
The Guardian: "The Times reported that a recorded message on an employee information line described a “code yellow”, the second-highest level in a three-tier alert system, for the day shift."

One name from CBS's own sources; one from a recorded message, via The Times, via the Guardian — second-hand twice over. The corpus nowhere equates them, and neither does the desk.

The cause account is where attribution does all the work. It climbs by rung, and the top rung is a named official:

── SHARED: php_cause · an_attribution_ladder ──
Fox Business: "Clayton specifically linked Tuesday's National Security Agency network outage to patching following the identification of a PHP vulnerability."
CBS News: "The National Security Agency's network outage Tuesday has been linked to an urgent patching of vulnerabilities in PHP, the programming language that powers the majority of all websites, multiple sources told CBS News."
CNN: "Multiple current US officials briefed on this week’s outage said it was not a cyberattack but instead appeared connected to the NSA’s handling of software updates for vulnerabilities in PHP"
New York Post: "The technical problems appear to have stemmed from the agency's efforts to install security patches addressing critical vulnerabilities in PHP, a widely used programming language that powers roughly 70% of the world's websites."
Fox News: "The issue appears to be technical in nature, the source added, though the precise cause has not been established."

Fox Business prints Clayton's link flat — "specifically linked" — and that phrasing is the strongest in the corpus. CBS attributes its link to multiple sources. CNN and the Post keep their hedges visible: "appeared connected," "appear to have stemmed from." And Fox News, in the same breath as its restoration report, prints that "the precise cause has not been established." Clayton's mechanism appears in PBS NewsHour's paraphrase: "the patching following last month's PHP alert has caused some systems to "not come back up" as expected." An official's on-record account, three hedged retellings, and one printed admission of an open question — all in one frozen set of pages.

Underneath the officials sits the agency's own Tuesday statement, and the file-honest note is what the statement did not say:

── SHARED: agency_statement · what_the_statement_left_out ──
Associated Press: ""The National Security Agency experienced temporary degradation during scheduled routine maintenance," the NSA said in a statement."
Reuters: ""While some internal systems were affected, mission-critical capabilities remain fully operational and our ability to defend national security continues," the NSA said."
The Guardian: "The statement did not name the network, say what caused the problem or how long it lasted, or say whether service had been fully restored."
Reuters: "Reuters could not independently determine the extent or the length of the outage."

The agency said maintenance; the officials said patching; the Guardian itemized the gaps; Reuters declared its own limit in a sentence any reader can check. The no-cyberattack caveat is constant across the files that carry it, and the vouching party rotates — "Multiple current US officials" at CNN, "multiple US officials" at the Post, "the sources" at NBC, Clayton by name at Fox Business and The Hill. In Clayton's own words, per The Hill: "This is not a cyberattack, and this is not a coordinated effort by a nation state. We've looked very closely." No file says ruled out. The desk does not upgrade the language it was given.

One corpus-shape observation: the Friday restoration appears in CNN, the New York Post and Fox News — CNN's account, relayed by the Post, which credits the voicemail and the source structure to CNN's reporting. Fox News attributes its restoration to its own source. What the wire files in this corpus carry is Tuesday's statement and Thursday's questions, not Friday's restoration. That is a fact about these seventeen records, not a claim about the world.

The reads, one per outlet in today's inventory:

── READ: CNN · resolution_with_two_counts ──
anchor: "has now been resolved, according to a source familiar with the matter and a voicemail inbox recording"
objective: the anchor seats the resolution on a source plus a recording; the same file carries two duration counts.
arrangement: the lede's "more than three days" and the body's "almost four days" sit far enough apart that a reader meets each without reconciling them.
confidence: strong

── READ: CBS News · thursday_up_and_protocol_name ──
anchor: "NSA Net as of right now is back up and running."
objective: the anchor timestamps a status claim to the moment of reporting; the same file carries the PHP link attributed to multiple sources.
arrangement: "as of right now" flags perishability; the "Code Gray" name arrives with no second source.
confidence: tentative

── READ: NBC News · thursday_still_down ──
anchor: "remained down on Thursday, resulting in some employees being ordered to work from home for a third day in a row"
objective: the anchor reports a continuing disruption through two people with knowledge; the caveat is sourced to them in the next breath.
confidence: tentative

── READ: New York Post · restoration_relay ──
anchor: "has been restored after nearly four days of disruptions that left scores of employees unable to log in, sources and officials said."
objective: the anchor carries CNN's reporting structure under the Post's own "restored" and its own duration round, with the CNN credit appearing further down the file.
confidence: strong

── READ: Fox News · patched_and_open_question ──
anchor: "has been patched and all employees are returning to work by this afternoon, a source familiar with the matter told Fox News on Friday."
objective: the anchor carries the Friday restoration on a single source; the next sentence prints that "the precise cause has not been established."
confidence: strong

── READ: Fox Business · claytons_flat_link ──
anchor: "Clayton specifically linked Tuesday's National Security Agency network outage to patching following the identification of a PHP vulnerability."
objective: the anchor carries the one named official's cause account in narration with no hedge in the wording; the quotes follow it.
confidence: strong

── READ: Associated Press · the_agencys_own_words ──
anchor: ""The National Security Agency experienced temporary degradation during scheduled routine maintenance," the NSA said in a statement."
objective: the anchor prints the agency statement whole; the following sentence notes the agency "did not provide any additional details on the cause of the outage or the scope of the disruption."
confidence: strong

── READ: Reuters · operational_claim_plus_declared_limit ──
anchor: "Reuters could not independently determine the extent or the length of the outage."
objective: the anchor states, in the wire's own voice, what the wire could not determine, beside the agency's operational claim above it.
confidence: strong

── READ: BBC News · statement_and_silences ──
anchor: "It did not specify when the issue began, nor when it would be resolved."
objective: the anchor itemizes what the statement omitted, at statement-length coverage.
confidence: strong

── READ: The Guardian · omissions_and_secondhand_name ──
anchor: "The statement did not name the network, say what caused the problem or how long it lasted, or say whether service had been fully restored."
objective: the anchor inventories the statement's silences; the "code yellow" report appears with its full chain — The Times, a recorded message — intact.
confidence: strong

── READ: The Hill · clayton_in_his_own_words ──
anchor: ""This is not a cyberattack, and this is not a coordinated effort by a nation state. We've looked very closely," Clayton said in an interview on CNBC"
objective: the anchor seats the no-cyberattack caveat with a named speaker rather than anonymous officials.
confidence: strong

── READ: PBS NewsHour · the_mechanism ──
anchor: "Clayton told Fox News that the patching following last month's PHP alert has caused some systems to "not come back up" as expected."
objective: the anchor carries the patching mechanism in the official's quoted fragments inside the broader outages-of-the-week frame.
confidence: strong

The close, scoped. Claim: whether the CBS "as of right now" status and the NBC "remained down" status describe the same hours of Thursday · status: unresolved · confidence: 0.0. probability mass ≠ 1.0. Claim: the restoration, as reported Friday by CNN, the Post and Fox News · status: established as attributed reporting, each with its named sourcing. High on the spans that located; all quoted text is from the frozen corpus.

## Sources

- CNN — "Outage at NSA’s highly classified communications network has been resolved, sources say": https://www.cnn.com/2026/11/20/politics/nsa-highly-classified-network-outage-resolved
- New York Post — "NSA's top-secret communications network restored after nearly 4-day outage": https://nypost.com/2026/11/20/us-news/nsas-top-secret-communications-network-restored-after-nearly-4-day-outage/
- Fox News — "Trump fires national cyber director as tech outages rattle the country": https://www.foxnews.com/live-news/tech-outages-trump-national-cyber-director-fired-11-20-26
- NBC News — "Classified NSA network is still down, leaving some staff working from home": https://www.nbcnews.com/politics/national-security/classified-nsa-network-still-leaving-staff-working-home-rcna610261
- CBS News — "National Security Agency network outage linked to software vulnerability": https://www.cbsnews.com/news/national-security-agency-network-outage-software-vulnerability/
- The Guardian — "National Security Agency network for internal communications goes down": https://www.theguardian.com/us-news/2026/nov/17/nsa-national-security-classified-communications-network-down
- Fox Business — "Jay Clayton addresses concerns amid widespread tech outages": https://www.foxbusiness.com/technology/jay-clayton-addresses-concerns-amid-widespread-tech-outages
- Associated Press — "Classified communications network at the National Security Agency goes down, defense official says": https://apnews.com/article/nsa-computer-network-down-22dc6be1bf1d1f5f86a7167f016e9526
- Reuters — "Classified US national security communications network hit by outage, NSA says": https://www.reuters.com/technology/highly-classified-us-national-security-communications-network-is-down-cnn-2026-11-17/
- BBC News (US & Canada) — "US National Security Agency's classified internal network reportedly goes offline": https://www.bbc.com/news/articles/cqvg2mg8g0pyo
- Al Jazeera — "NSA attributes US network outage to routine ‘maintenance’ activities": https://www.aljazeera.com/news/2026/11/17/nsas-classified-internal-communications-network-reportedly-faces-outage
- CBC News — "Multiple tech outages have Americans asking: Can somebody fix this?": https://www.cbc.ca/news/world/outages-faa-banks-microsoft-nsa-are-they-related-9.7425366
- Fox News — "NSA's highly classified communications network disrupted by widespread outage": https://www.foxnews.com/politics/nsa-highly-classified-communications-network-disrupted-widespread-outage
- Washington Examiner — "NSA's classified communication channel goes down": https://www.washingtonexaminer.com/policy/national-security/4806055/national-security-agency-communication-channel-outage/
- The Washington Times — "High-level U.S. national security communications network knocked offline: Report": https://www.washingtontimes.com/news/2026/nov/17/high-level-us-national-security-communications-network-knocked/
- The Hill — "Trump officials seek to ease anxiety over sweeping tech outages": https://thehill.com/homenews/administration/6228962-trump-officials-seek-to-ease-anxiety-over-sweeping-tech-outages/
- PBS NewsHour — "Are tech disruptions and and outages the new normal?": https://www.pbs.org/newshour/nation/are-tech-disruptions-and-and-outages-the-new-normal
