🔍 Read the full analysis: From Flight Disruptions To Email Issues: A Week Of US Tech Outages on ThorstenMeyerAI.com
Get smart everyday buys delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Six major outages affected US technology and services from November 12 to 17, disrupting business email, flights, banking transactions, airline operations and government networks. Organizations have attributed incidents to software defects, network data flooding, hardware bugs, an internal update or scheduled maintenance; officials say they have no evidence the outages were linked or caused by an attack.
Six outages disrupted major US technology and services between November 12 and 17, affecting Microsoft 365 email, air travel, JPMorgan Chase transactions, United Airlines operations, Apple services and an NSA network. The organizations have described separate technical causes, and US officials say they have no evidence of a coordinated cyberattack or a connection among the incidents.
The outages came in quick succession. Microsoft 365 email service failed for many business users on November 12. The next day, the Federal Aviation Administration stopped departures at US airports. On November 16, JPMorgan Chase customers experienced stalled transactions, while United Airlines said a technology issue prevented it from sending pilots final aircraft weight information. On November 17, Apple reported problems with iCloud and the App Store, and the National Security Agency’s classified internal network went down.
The causes reported so far differ. Microsoft’s preliminary incident report identifies a latent software defect, a network gateway failover and reduced server capacity. The FAA said data flooded its network amid router work at two remote sites. JPMorgan Chase cited “a software bug in on-premise hardware systems”; United described “a technology issue”; and Apple said an “internal update” was involved. The NSA attributed its outage to scheduled routine maintenance, which Director of National Intelligence Jay Clayton linked to security patching.
Microsoft is the only organization in the source material to have published a technical post-incident report, and it is preliminary. The company said the outage lasted 23 hours and 50 minutes, from 16:20 UTC on November 12 until 16:10 UTC on November 13. It reported that, at the worst point, more than 80% of affected servers were unresponsive. Microsoft’s final report was due November 20.
The range of services affected shows how disruptions to shared infrastructure can reach beyond the organization operating it. Email failures can interfere with calendars and workplace tools; airline systems support decisions needed before departure; and banking services sit within networks of payments used by customers and businesses. When those systems falter, the effects can spread to people and organizations that did not cause the underlying problem.
The documented explanations also point to operational risks that do not require a common attacker. Microsoft described a failure involving a software defect and reduced capacity. The FAA reported that data flooding destabilized legacy equipment during work at remote sites. Clayton said institutions were patching systems after newly found vulnerabilities and that systems do not always recover as expected. His comments were a general explanation, however, not a finding that patching caused the other outages.
For organizations, the incidents underline the need to plan for failures in systems and vendors they depend on, including communication and payment services. For users, a backup way to pay or reach important information can help during an outage. Those are practical precautions, not evidence that a wider attack is underway.
Popular right now

Bose QuietComfort Ultra Wireless Noise Cancelling Earbuds, 2nd Gen, with 20W 2-Port Wall Charger

TCL 85-Inch QM6K QLED Mini LED 4K HDR Smart Google TV, 144Hz

Bose QuietComfort Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones, White Smoke
As an affiliate, we earn on qualifying purchases.
The Week’s Outage Timeline
The sequence began with Microsoft 365 on Thursday, November 12. Microsoft said a defect introduced by a change whose rollout began in July left Windows servers vulnerable to becoming overwhelmed under certain load conditions. About 15 hours before the outage, Teams shifted from an alternative network gateway to the primary gateway also used by Exchange Online. Microsoft said nearly 14% of that gateway’s server capacity was already out of service because of an unrelated issue, contributing to failures that spread across servers.
On Friday, November 13, the FAA issued a nationwide ground stop. Its written account said legacy equipment became unstable as data flooded the FAA FTI network at a rate of 1,000 connection attempts every four to five seconds. The initial investigation pointed to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where contractor L3Harris had been carrying out router work. The stop was lifted after four hours and 23 minutes. The FAA counted about 12,462 affected flights that Friday, including 9,082 cancellations by major airlines; that figure was not limited to cancellations directly caused by the ground stop.
The remaining incidents followed on Monday and Tuesday. JPMorgan Chase and United Airlines reported service problems Monday, followed by Apple and the NSA on Tuesday. Reuters reported that Microsoft’s disruption also affected government bodies and airline email services outside the United States. Flight disruption figures cited by NPR from FlightAware and Cirium use different time windows and measures, so they should not be treated as a single count of flights caused by the FAA stop.
““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.””
— US Secretary of State Marco Rubio, speaking in Manila
What Investigators Have Not Established
As of 13:30 UTC on November 18, officials said they had no evidence that the outages were linked or caused by a cyberattack. That is a statement about the evidence available at that point, not proof that every investigation is complete. Microsoft’s account remained preliminary, and the FAA described its findings as initial.
Public technical detail is uneven. The source material provides no comparable engineering reports for the JPMorgan Chase, United Airlines or Apple incidents, and the NSA explanation is limited to routine maintenance and patching. It is also unclear whether all affected users and services have fully recovered, whether the organizations will publish further findings, or whether any common contributing factors will emerge. Clayton’s comments about patching were a general assessment; they do not establish a shared cause.
Final Reports and Service Follow-Up
Microsoft’s final report was expected on November 20, and may add detail about the defect, network capacity and recovery. The FAA’s initial findings identify the locations and network behavior under review, but the source material gives no date for a final account. Further statements from JPMorgan Chase, United Airlines, Apple and the NSA could clarify the duration, scope and technical causes of their incidents.
Until more reporting is available, the confirmed picture remains six separate disruptions with distinct explanations supplied by the organizations involved. Readers should watch for final technical reports and service updates rather than treating speculation about a coordinated attack as established fact.
Key Questions
Were the six outages caused by a coordinated cyberattack?
Officials said they had no evidence that the incidents were related or caused by an attack, based on information available by November 18. Investigations were not all complete.
Which outage has the most detailed public explanation?
Microsoft 365 had the most detailed account in the source material: a preliminary report described a latent software defect, a gateway failover and reduced server capacity. Microsoft’s final report was due November 20.
What did the FAA say caused the flight disruption?
The FAA said data flooding its FTI network destabilized legacy equipment. Its initial investigation pointed to router work at a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas.
Did all of the organizations give detailed technical findings?
No. Microsoft published a preliminary technical report, and the FAA provided an initial account. The statements attributed to JPMorgan Chase, United, Apple and the NSA offered less technical detail.
Source: ThorstenMeyerAI.com
