US Tech Outages This Week: The Disruptions Across Banks, Flights, Email, And The NSA
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: US Tech Outages This Week: The Disruptions Across Banks, Flights, Email, And The NSA on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

Six reported outages from Nov. 12 to Nov. 17 disrupted Microsoft 365 email, US flight operations, JPMorgan Chase transactions, United Airlines pilot data, Apple services and an NSA network. Organizations have described separate technical or maintenance-related causes, and officials say they have no evidence the incidents were connected or the result of an attack. Microsoft has published a preliminary technical report; several other investigations remain incomplete.

Six outages disrupted email, US flight operations, banking transactions, airline operations and government networks between Nov. 12 and Nov. 17, but the organizations involved have so far described separate technical or maintenance issues, not a coordinated attack. US officials said they had no evidence linking the incidents; several investigations are still under way.

The incidents affected Microsoft 365 on Nov. 12-13, a Federal Aviation Administration system on Nov. 13, and services used by JPMorgan Chase and United Airlines on Nov. 16. Apple services and an NSA internal network experienced problems on Nov. 17, according to the source report. The disruptions touched services people and businesses rely on for communication, travel, payments and access to digital products.

The causes organizations have disclosed differ. Microsoft’s preliminary report described a software defect, a network failover and reduced gateway capacity that together contributed to a cascading server failure. The FAA said data flooded its network during router work at two remote sites. JPMorgan Chase cited a software bug in on-premise hardware systems; United described a technology issue; Apple said an internal update was involved. The NSA characterized its outage as scheduled routine maintenance.

These accounts are not equally detailed. Microsoft is the only organization in the supplied material to have published a technical report, and it is preliminary. The other explanations are brief statements or initial findings. The source material provides no confirmed cause linking the incidents, and it does not establish that the outages had a shared technical origin.

At a glance
recapWhen: Incidents reported Nov. 12-17, 2026; in…
The developmentSix outages affecting major US technology-dependent services in one week have prompted scrutiny, but the organizations and officials cited in the source report separate causes and no evidence of a coordinated attack.

Disruptions Across Essential Services

The effects show how a failure in a technical service can reach people well beyond the system’s operator. The Microsoft 365 outage affected email and related services, while the FAA disruption prompted a nationwide ground stop. Payment delays can inconvenience bank customers and businesses, and an airline’s inability to send pilots required weight data can affect departure operations.

For the FAA incident, the scale was substantial: the agency counted about 12,462 flights affected on Friday, including 9,082 cancellations by major airlines, according to the source report. That figure is the FAA’s count of affected flights; it does not mean every cancellation was directly caused by the ground stop. The disruptions also underline the risks of dependence on shared systems and infrastructure, though the available evidence does not show that one common failure caused this week’s incidents.

For organizations, the reported accounts point to practical areas to examine: how changes are tested and deployed, whether older equipment can handle new network conditions, and what fallback options exist when a core service fails. Those are implications of the incidents, not findings that every affected organization had the same weakness.

De'Longhi Rivelia Automatic Espresso Machine with Milk Frother

De'Longhi Rivelia Automatic Espresso Machine with Milk Frother

Shark PowerDetect Robot Vacuum and Mop Combo with 60-Day Self-Emptying Base (AV2800ZE)

Shark PowerDetect Robot Vacuum and Mop Combo with 60-Day Self-Emptying Base (AV2800ZE)

De'Longhi Stilosa Compact Manual Espresso Machine with Manual Milk Frother

De'Longhi Stilosa Compact Manual Espresso Machine with Manual Milk Frother

As an affiliate, we earn on qualifying purchases.

A Week of Separate Outages

The sequence began with Microsoft 365 email on Thursday, Nov. 12. Microsoft’s status information put the disruption between 16:20 UTC on Nov. 12 and 16:10 UTC on Nov. 13, a total of 23 hours and 50 minutes. Its preliminary post-incident report, dated Nov. 15, said a latent defect had been introduced in a change whose deployment began in July. It also described a Teams failover to a primary gateway shared with Exchange Online and about 14% of gateway server capacity being unavailable because of an unrelated issue from the previous day. Microsoft said the resulting traffic shift contributed to cascading failures, with more than 80% of servers unresponsive at the low point.

On Nov. 13, the FAA issued a ground stop affecting airports across the United States. Its written account said legacy equipment became unstable as connection attempts flooded the FAA telecommunications network, at a rate of 1,000 attempts every four to five seconds. The FAA’s initial investigation 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 source cuts off before giving further detail on that work or the FAA’s final findings.

The remaining incidents were reported on Nov. 16 and 17. JPMorgan Chase and United Airlines each provided short descriptions of their technical problems; Apple attributed its service issue to an internal update. For the NSA network outage, Director of National Intelligence Jay Clayton connected the incident to scheduled security patching. Clayton also said many institutions were patching vulnerabilities, but his broad explanation is not a confirmed cause for the other outages.

“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.”

— Marco Rubio

Investigations Still Incomplete

As of the source report’s stated cutoff, 13:30 UTC on Nov. 18, only Microsoft had published a technical report, and that report was preliminary. Microsoft’s final report was expected on Nov. 20. The supplied information does not include final findings from the FAA, JPMorgan Chase, United Airlines, Apple or the NSA.

Officials’ statements that they had no evidence of an attack or connection reflect the information available at the time. They do not prove that every technical detail is known or that future findings cannot change. The source material also does not provide outage durations, affected-user counts or detailed technical explanations for several of the incidents. It is not clear how many customers or operations were affected by the JPMorgan Chase, United, Apple and NSA outages.

Although the reported causes include software defects, network conditions, updates and maintenance, the available facts do not establish a single shared cause. Nor does the material confirm the source report’s broader suggestion that the incidents share a common pattern beyond changes or maintenance intersecting with system weaknesses.

Final Reports and Service Reviews

The next stated milestone is Microsoft’s final post-incident report, expected Nov. 20. It may add detail to the company’s preliminary account, but the source does not say whether the other organizations have set dates for publishing their findings.

For readers, the immediate picture remains one of separate outages with varying levels of explanation. Organizations affected by the disruptions may release additional information about their investigations, fixes and safeguards. Until those updates are available, claims of a coordinated attack or a single cause go beyond what officials and companies have confirmed.

The source report advises businesses to review dependencies on shared services, prepare alternatives for communication and payment processing, and treat changes to live systems as potentially disruptive. It also suggests that users keep another payment option and offline copies of information they may need. These are precautionary recommendations, not official requirements announced by the organizations involved.

Key Questions

Were the six outages caused by a cyberattack?

No evidence of an attack had been reported in the source material as of 13:30 UTC on Nov. 18. The organizations described technical or maintenance-related issues, and Secretary of State Marco Rubio said officials had no evidence the incidents were related. Investigations were not all complete.

Which services were affected?

The incidents involved Microsoft 365 email and related services, FAA flight operations, JPMorgan Chase transactions, United Airlines pilot data, Apple’s iCloud and App Store, and an NSA internal network, according to the source report.

What caused the Microsoft 365 outage?

Microsoft’s preliminary report described a latent software defect, a Teams failover to a gateway shared with Exchange Online, and reduced gateway capacity. Microsoft said these factors contributed to cascading server failures. Its final report was expected on Nov. 20.

What does the FAA say caused the flight disruption?

The FAA said data flooded its network during router work at two remote sites, destabilizing legacy equipment. Its initial investigation pointed to sites in Amarillo, Texas, and El Dorado, Arkansas; final findings were not included in the source material.

Are all the causes known?

No. Microsoft had released a preliminary technical report, while several other organizations had provided only short explanations or initial accounts. Final findings and the full extent of several outages remain unclear.

Source: ThorstenMeyerAI.com

You May Also Like

Windows 11½

Search and coverage interest in “Windows 11½” is spiking, but the reason is unconfirmed and no specific announcement is verified.

Show HN: Mindwalk – Replay coding-agent sessions on a 3D map of your codebase

Mindwalk introduces a new tool enabling developers to replay coding sessions on a 3D map of their codebase, showcased on Show HN.

What To Know About Meta’s AI Agent, Muse, And Message Access

Meta’s Muse can use connected messages and other data to assist its users. Here’s what is confirmed about access, memory, controls and open questions.

Your Experts Have Partners. There’s HOPE For Keeping Them Together

Hugging Face researchers say HOPE accounts for expert pairings when pruning MoE models, reporting its strongest comparative results at 50% pruning.