🔍 Read the full analysis: US Tech Outages Explained: A Week Of Problems For Banks, Flights, Email, And The NSA on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Six outages from November 12 to 17 disrupted Microsoft 365, US air travel, JPMorgan Chase services, United Airlines operations, Apple services and an NSA network. The organizations have cited separate technical issues, maintenance or changes to their systems; officials say they have no evidence the incidents were linked or caused by an attack. Several investigations remain incomplete.
Six outages disrupted email, US flights, banking, airline operations, Apple services and a classified government network between November 12 and 17, according to accounts from the organizations involved. They have cited separate technical problems and maintenance, while US officials say they have no evidence so far of a coordinated attack or a link between the incidents.
The outages affected systems people and organizations rely on for daily operations. Microsoft 365 email was unavailable to many business users from 16:20 UTC on November 12 until 16:10 UTC on November 13, a period of 23 hours and 50 minutes, according to Microsoft’s status information. The disruption also affected services tied to email, including calendars and some SharePoint and Teams functions.
On November 13, the Federal Aviation Administration ground-stopped departures at US airports while it dealt with a network problem. The source says the stop began at 3:53 p.m. Eastern Time and ended at 8:16 p.m., after 4 hours and 23 minutes. The FAA reported about 12,462 affected flights on Friday, including 9,082 cancellations by major airlines; that figure does not mean every cancellation was directly caused by the stop.
Other reported incidents followed. On Monday, JPMorgan Chase customers experienced stalled transactions, and United Airlines said a technology issue prevented it from sending pilots final aircraft weight information needed for takeoff. On Tuesday, Apple reported problems involving iCloud and the App Store, while the National Security Agency’s classified internal network went down. The supplied material does not give precise outage durations or user totals for these incidents.
Disruptions to Essential Services
The outages show how technical problems at central systems can affect services well beyond the equipment or software that failed. An email disruption can interrupt calendars and workplace tools; a flight-data problem can hold departures; and banking delays can affect customers and businesses waiting for payments to clear.
The incidents also highlight the consequences of relying on shared infrastructure and limited fallback options. Microsoft’s preliminary account describes a failure that spread across servers after traffic shifted to remaining gateway capacity. That is a company-reported explanation for its outage, not evidence that the other incidents had the same mechanism. For users, the practical effect is that routine services may be unavailable even when there is no attack and no single event behind multiple failures.
Popular right now

Ninja Prestige Smart XL 10-in-1 Air Fryer and Countertop Oven with Pro Cook System, Stainless Steel, DT551

Dyson Airwrap i.d. Multi-Styler with Bluetooth Connectivity

Vitamix 5-Speed Immersion Blender, 625-Watt, Stainless Steel/Black
As an affiliate, we earn on qualifying purchases.
What Organizations Have Reported
The available explanations differ. Microsoft’s preliminary incident report, dated November 15, identified a latent software defect, a shift between network gateways and reduced gateway capacity. The company said the change associated with the defect began deploying in July. Microsoft said the combination led to cascading server failures; its final report was expected November 20.
The FAA attributed its outage to data flooding its legacy FTI network at a rate of 1,000 connection attempts every four to five seconds. Its initial investigation pointed to router work at a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas. The source material does not include the full FAA account or a final investigation finding.
JPMorgan Chase described its problem as “a software bug in on-premise hardware systems.” United called its incident “a technology issue,” Apple said an “internal update” was involved, and the NSA described its outage as “scheduled routine maintenance.” Director of National Intelligence Jay Clayton linked the NSA disruption to security patching. These brief descriptions do not provide the same level of technical detail as Microsoft’s preliminary report.
““A technical issue not related to cyber or AI / agents.””
— Microsoft, in a statement on November 13
Investigations Still Incomplete
No evidence of a shared attack has been reported by the organizations or officials cited in the source material. That is the status of the evidence described as of November 18, not proof that every technical cause has been established. Rubio’s statement also was not presented as the result of a finished investigation into all six events.
Microsoft is the only organization in the material to have published a technical post-incident report, and it described that report as preliminary. The FAA’s investigation was also described as initial. For JPMorgan Chase, United, Apple and the NSA, the available statements give limited detail about the underlying failures, their duration and the full effect on users. The material does not establish that the incidents shared a cause, or that patching was responsible for outages beyond the NSA event.
Final Reports and Service Resilience
Microsoft’s final report was due November 20, according to the company’s stated timeline. The FAA and the other organizations may provide further findings, but the supplied information gives no publication dates for their next updates. Until more detailed accounts are released, the causes and scope of several outages remain only partly documented.
For businesses, the week points to practical steps that do not depend on assuming a common cause: understand which outside services operations rely on, plan alternate ways to communicate and handle payments, and treat changes to widely used systems as a source of operational risk. Users can keep a second payment option and offline access to information they may need. These measures do not prevent outages, but can reduce the disruption while providers restore service.
Key Questions
Were the six outages caused by one coordinated attack?
No link or attack has been established in the information available as of November 18. Officials and the organizations said they had no evidence of a cyberattack or a connection between the incidents, though investigations were incomplete.
Which outage lasted the longest?
The source gives a precise duration for Microsoft 365: 23 hours and 50 minutes, from 16:20 UTC on November 12 to 16:10 UTC on November 13. It does not provide comparable durations for all the other incidents.
What caused the FAA flight disruption?
The FAA said data flooded its legacy FTI network, destabilizing equipment. Its initial investigation pointed to two sites where contractor L3Harris had been deploying router work. The available account does not provide a final investigation finding.
Did the FAA ground stop cause every flight cancellation that day?
No. The FAA reported about 12,462 affected flights, including 9,082 cancellations by major airlines, but the source explicitly says not all cancellations were directly caused by the ground stop.
What should customers and businesses do during similar outages?
Keep backup ways to communicate and pay, and retain offline copies of information needed for essential tasks. Businesses can also identify service dependencies and plan how to operate if a key provider is unavailable.
Source: ThorstenMeyerAI.com
