🔍 Read the full analysis: What’s The Common Thread In A Week Of US Tech Outages At Banks And The NSA? on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Six outages affecting US technology companies, banks, airlines and the NSA occurred between November 12 and 17, 2026. The organizations cited separate technical causes, many involving changes to live systems; officials said they had no evidence the incidents were attacks or connected, while investigations remain incomplete.
Six outages affecting Microsoft 365, US aviation, JPMorgan Chase, United Airlines, Apple and the National Security Agency occurred during the week of November 12, but the organizations have reported separate technical causes and officials say they have no evidence of a coordinated attack. The incidents have drawn attention to a more practical shared risk: changes to live systems and dependencies that can disrupt many users when something goes wrong.
The incidents began with a Microsoft 365 email outage on November 12, followed by a nationwide Federal Aviation Administration ground stop on November 13. On November 16, JPMorgan Chase customers experienced stalled transactions and United Airlines reported a technology issue affecting the delivery of final aircraft weights to pilots. Apple services faltered on November 17, the same day the NSA said its classified internal network had gone down. The source material places the sequence across six incidents, but does not provide complete timelines for every service disruption.
The causes described by the organizations are not identical. Microsoft’s preliminary report identified a latent software defect, a shift in network traffic to a primary gateway, and reduced server capacity. The FAA said data flooding its network made legacy equipment unstable during router work at two remote sites. JPMorgan cited “a software bug in on-premise hardware systems,” United said “a technology issue,” Apple described “an internal update,” and the NSA cited scheduled routine maintenance. National Intelligence Director Jay Clayton linked the NSA outage to security patching.
By the evening of November 17, Secretary of State Marco Rubio said the government had no evidence that the incidents were connected. Clayton also said there was no indication of an attack. Those statements describe the evidence available at the time, not a final determination: Microsoft was the only organization in the source material to have published a technical report, and it was preliminary. Its final report was expected November 20.
The incidents affected different services, but each shows how a technical fault can reach people well beyond the system where it begins. Microsoft email supported calendars and other workplace services. The FAA network supports aviation operations, while airline weight-and-balance information is needed before flights can depart. A disruption at a bank can delay customer transactions, and failures in widely used cloud services can affect access to apps and communications.
The common lesson supported by the reports is not that one hidden cause produced all six outages. Rather, routine changes can interact with older equipment, reduced capacity or a heavily relied-upon service. When organizations have limited alternatives for a gateway, payment path or operational system, a local fault may affect a much larger group. Businesses can use the incidents to review change controls, vendor dependencies and fallback plans; users may benefit from having another way to pay or access essential information.
Products Worth Considering

Sonos Arc Ultra Dolby Atmos Soundbar, Black

LG 27GR83Q-B 27-inch Ultragear QHD IPS Gaming Monitor

Amazon Kindle Scribe (16GB) with Premium Pen, Tungsten
As an affiliate, we earn on qualifying purchases.
The Incidents Behind the Pattern
Microsoft’s outage lasted from 16:20 UTC on November 12 to 16:10 UTC on November 13, according to its final service status, a total of 23 hours and 50 minutes. Its November 15 preliminary report said a defect in a change whose deployment began in July left Windows servers vulnerable to becoming overwhelmed under certain load conditions. It also cited a Teams failover to the primary gateway used by Exchange Online and about 14% of gateway server capacity being unavailable because of a separate issue. Microsoft said the resulting traffic shift caused a cascading failure; at the low point, more than 80% of servers were unresponsive.
For the FAA incident, the agency said its legacy equipment became unstable as data flooded the FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. Its initial account pointed to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where contractor L3Harris had been deploying equipment. The supplied material does not include the complete FAA account or establish the exact contribution of each site.
Clayton said many institutions were applying patches after newly found vulnerabilities and that systems do not always restart as expected. He tied that explanation to the NSA outage; it is his general interpretation of the broader week, not a confirmed cause for the other organizations. The stated causes for JPMorgan, United and Apple are brief, and no technical reports for those incidents are included in the material.
“We have zero evidence whatsoever, we have no indication, no evidence, and no reason to believe at all that any of these incidents are related to each other.”
— Secretary of State Marco Rubio, speaking in Manila on November 17
Investigations Have Not Finished
It remains unclear whether any technical conditions overlapped beyond the broad theme of changes and system dependencies. No evidence of a link or attack had been reported by the officials and organizations cited as of the source material’s November 18 update, but that does not establish that every investigation is complete. Microsoft’s findings are preliminary, and its final report was due November 20.
Several accounts also lack detail. The source material does not give full technical explanations or recovery timelines for JPMorgan, United, Apple or the NSA, nor does it establish the precise operational sequence behind every outage. Clayton’s view that patching may explain a wider pattern should not be treated as a confirmed cause for incidents other than the NSA network disruption.
Final Reports and Recovery Details
The next stated milestone is Microsoft’s final post-incident report, expected November 20. That report may clarify how the software defect, gateway failover and unavailable capacity combined, and whether the company has identified additional safeguards. Further detail from the FAA and the other affected organizations would be needed to compare their causes more closely.
For now, the evidence supports separate outages with distinct reported causes, not a single established event linking them. Businesses and public agencies will be watching for findings on how changes were tested, how older systems handled new traffic, and what backup options were available. Until the organizations publish more detail, the extent of any shared operational weakness remains unsettled.
Key Questions
Were the six outages caused by a cyberattack?
No attack was confirmed in the source material. Officials and the organizations said they had no evidence of an attack as of November 18, 2026; investigations were not all described as complete.
What common thread did officials identify?
The reports point to separate technical problems, several involving changes to live systems or weaknesses exposed during changes. That is a shared operational theme, not proof of a single cause or connection.
Which outage has the most detailed explanation so far?
Microsoft had published a preliminary technical report describing a software defect, a network gateway failover and reduced server capacity. The company’s final report was expected November 20.
What did the FAA say caused its disruption?
The FAA said data flooding its network made legacy equipment unstable during router work at two remote sites. Its account cited 1,000 connection attempts every four to five seconds.
Are all six investigations complete?
The source material does not say that they are. Microsoft’s account was preliminary, and detailed technical explanations were not provided for several other incidents, so important findings remain outstanding.
Source: ThorstenMeyerAI.com
