Cyber chief Sean Cairncross is out as flights, email and spy networks fail
The White House confirmed its national cyber director is leaving, and a source close to it calls it a firing, just as flights, email and an intelligence network failed. Officials say the failures have nothing to do with each other, and the public is owed more than that assurance.
When the official in charge of defending a government's computers departs, in what a source close to the White House calls a firing, in the same week the computers keep failing, and the government then says the failures have nothing to do with one another, it has told us what it believes. It has not told us why we should believe it.
Sean Cairncross is out as US national cyber director. A White House official confirmed to CNN that he was leaving, and a source close to the White House described it as a firing that President Donald Trump supported because Cairncross lacked strong cyber credentials [3]. The week around his departure was ugly. Departing air travel halted nationwide, a Microsoft outage knocked out email services, and the National Security Agency's network was temporarily disrupted [1][2]. France 24 also reported disruptions to banking systems [1].
My position is simple. "Unrelated" is a conclusion, and the public has been handed the conclusion without the work. In a country that runs its airspace, its payments and its intelligence on networked software, that is not good enough.
What the administration has actually said
I want to be fair to the White House, because its case is not foolish. On November 18 it released a statement saying it had no evidence the incidents were related to one another or caused by hackers, criminals, a foreign government or any other malign actor [5]. National Security Adviser Marco Rubio put it more bluntly: "The Microsoft incident has nothing to do with what we saw with the FAA. The FAA has nothing to do with what we saw with the banks a few days ago." [5]
Director of National Intelligence Jay Clayton offered the closest thing to a mechanism. The incidents, he said, were separate service outages associated with maintenance and technical changes, not a coordinated or state-sponsored attack. Systems being patched or upgraded did not always return as expected, he said, including when one system had to hand its work off to another [5].
That may be exactly right. Big systems break in dull ways, and the dullest cause is usually the true one. Officials who refused to cry cyberattack at the first sign of trouble deserve some credit, because a false alarm about a foreign strike carries its own dangers. Nothing establishes that the outages caused Cairncross's removal. I will not pretend otherwise.
But the White House's own explanation has a hole in it, and the hole is the whole story.
Separate incidents, similar explanations
Rubio says three failures have nothing to do with one another. Clayton associates the outages with maintenance and technical changes, and with systems that did not come back as expected after being patched or upgraded. Those two statements sit awkwardly together. If several large systems failed in the same week and officials point to the same broad family of cause, then "nothing to do with each other" is too strong, even if no hostile hand was involved.
I am not saying there is a common cause. I am saying the administration has not shown there is not one. Its release says it has no evidence of a link, which is a different claim from Rubio's flat denial [5]. Absence of evidence is what you have on the first day of an investigation. It is not what you announce at the end of one. The White House's account is a statement from the administration itself, and it has not published an incident-by-incident finding of what failed in each system [1][2][5].
The questions are not exotic. What failed at the FAA, and for how long? What exactly happened to the NSA's network? Have all the affected systems returned to normal? Who owned the change that went wrong in each case, and who signed off on it? What did investigators check before they ruled out hostile action? If "separate" is true, each of those answers will say so, and the White House should be glad to publish them.
A credentials problem with an odd timeline
The departure itself raises a second question. According to the source close to the White House, the president backed the firing because Cairncross lacked strong cyber credentials [3]. Defense One reports the same rationale, attributed to its own sources [2]. Neither account comes from the White House on the record.
Take the explanation at face value and the timeline is strange. The White House announced on August 2, 2025 that the Senate had confirmed Cairncross, calling him the president's principal adviser on national cybersecurity policy and strategy [4]. Whatever his résumé held then, it held the same on that day. If credentials are the reason, they did not shrink during a bad week for the network. Either someone knew about the gap when he was put in the job, or the gap became a problem only when the screens went dark. Neither answer is flattering, and the public is entitled to know which it is.
Cairncross, in his statement to CNN, said he was "incredibly proud" of work to strengthen America's cybersecurity, protect critical infrastructure and confront foreign threats, and to "position America to lead the world in Super Intelligence." [3] The statement as CNN quotes it does not mention the week's outages.
Who is minding the shop
The Office of the National Cyber Director exists to advise the president on cybersecurity and to coordinate cyber policy across federal agencies [2]. Its value is in the coordinating. An air traffic system, a spy agency's network and a commercial email service sit in different hands, and someone has to be able to look across all of them and ask whether they share a weakness.
That job now falls, in an acting capacity, to Kirsten Davies, the Defense Department's chief information officer, whom the White House named to take over [3]. She was confirmed by the Senate for her Pentagon post. A permanent national cyber director would need confirmation as well [3]. We do not know what authority or reporting line she will have in the acting role, how long she is expected to hold it, or when a nominee will arrive. We also do not know what standard the White House will apply to that nominee, if the credentials explanation is the true one.
I spent twenty years as a foreign correspondent watching governments explain things. The explanations that held up were the ones with details in them. The ones that fell apart were short, confident and delivered before the investigation was finished. "Nothing to do with each other" has the shape of the second kind. It may yet prove correct, and I would be relieved if it did. But relief is not an audit.
What to demand
Three things, none of them radical.
First, a written post-incident account for each outage, from the agency or company that ran the system, saying what failed, what was affected, how long it lasted and what will stop it happening again. Companies and agencies do this routinely when they want to be believed.
Second, an explanation of what evidence supports the claim that the incidents were separate, and who checked it. If the Director of National Intelligence is willing to say the word "not" about a state-sponsored attack, he should be willing to say what was examined.
Third, a plain statement from the White House about why Cairncross is gone and what the next director will be expected to know. A president is free to dismiss a subordinate. He is not free of the obligation to say what the job is for. Congress, which has to confirm the successor, is the natural place to ask.
The public lives downstream of all these systems. When they stumble, we are the ones standing at the departure gate with a dead screen and a missing email. A government that wants our trust on the question of why should expect to be asked, and should be quicker to answer than it has been.
The week's outages were declared unrelated within days. The explanations are still on their way.
Our call
A committee of the US House or Senate holds a public hearing, or a hearing session with a published title or stated purpose, that examines the November 2026 technology outages affecting air travel, Microsoft email and government networks.
A week of failures across air travel, email and an intelligence network, followed by the departure of the cyber chief whose successor needs Senate confirmation, gives Congress both a motive and a vehicle, while the administration has offered only a broad account of causes.
Elena Marsh
Elena MarshSenior writerWrites the long pieces that make people read to the end. Believes every story is a history story if you go back far enough, and usually goes back just far enough.Model: Claude Sonnet 5.5 says
45%. Jev says 26%.
By February 15, 2027. How we will check: Check the official hearing calendars and records of the House and Senate committees (for example Homeland Security, Commerce, Intelligence or Armed Services). The call resolves yes if any hearing held between November 27, 2026 and February 15, 2027 lists the outages in its title, its stated subject or its published witness statements.
Open · Every call we made
Every edition in brief, three times a day, on our Telegram channel, on Bluesky and on Threads.
Spotted an error? Tell the editors
- White House fires national cyber director over widespread outages - France 24 France 24
- White House fires cyber director in wake of outages, sources say - Defense One defenseone.com
- White House national cyber director being replaced as nation reels from tech outages | CNN Politics edition.cnn.com
- U.S. Senate Confirms Sean Cairncross as the National Cyber Director - The White House whitehouse.gov
- "No Indication of a Cyberattack": DNI Clayton and Secretary Rubio on Recent Tech Outages - The White House whitehouse.gov



