🔍 Read the full analysis: A Closer Look At US Tech Outages Affecting Banks, Flights, Email, And The NSA This Week on ThorstenMeyerAI.com
Get the latest gadgets 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 outages from Nov. 12 to Nov. 17 disrupted Microsoft 365, US air travel, JPMorgan Chase transactions, United Airlines operations, Apple services and an NSA network. The organizations have cited separate technical issues or maintenance, and officials say they have no evidence the incidents were linked or caused by an attack; investigations remain incomplete.
Six outages disrupted email, flights, banking, airline operations, Apple services and an NSA network between Nov. 12 and Nov. 17, but the organizations involved have described separate technical problems or scheduled maintenance—not a confirmed coordinated attack. As of 13:30 UTC on Nov. 18, officials said they had no evidence linking the incidents, while several investigations were still underway.
The outages began Thursday, Nov. 12, when many Microsoft 365 business users lost access to Exchange Online email and related services. Microsoft’s status record puts the disruption at 23 hours and 50 minutes, ending Nov. 13. A preliminary post-incident report dated Nov. 15 attributed the failure to a latent software defect, a shift of Teams traffic to a gateway also supporting Exchange Online, and about 14% of gateway server capacity being unavailable because of a separate issue. Microsoft said the resulting traffic surge caused cascading server failures; at the worst point, more than 80% of servers were unresponsive.
On Nov. 13, the Federal Aviation Administration ordered a nationwide ground stop. The FAA said legacy equipment became unstable when data flooded its network, with 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 FAA’s Friday count was about 12,462 flights affected, including 9,082 cancellations by major airlines; the agency cautioned that not all were directly caused by the ground stop. FlightAware and Cirium figures reported by NPR used different counts and measures.
Further disruptions followed on Nov. 16 and 17. JPMorgan Chase said a software bug in on-premise hardware systems caused transaction delays. United Airlines described a “technology issue” that prevented it from sending pilots final aircraft weights needed for departure. Apple cited an “internal update” after iCloud and App Store services faltered. The NSA said its classified internal network outage resulted from scheduled routine maintenance; Director of National Intelligence Jay Clayton linked that outage to security patching. The supplied material does not include technical reports for these incidents.
The incidents show how a problem inside one technical system can affect services people and institutions rely on: email supports workplace coordination, banking systems process payments, and airline systems help crews prepare flights. In Microsoft’s case, the company described a gateway serving both Teams and Exchange Online, while unavailable capacity contributed to a wider failure. The FAA’s account similarly points to network data flooding that destabilized legacy equipment.
Those examples do not establish a single cause across the week. Rather, the reported explanations share an operational risk: changes to live systems and dependencies on shared infrastructure can expose weaknesses or magnify a local fault. For businesses, the disruptions are a reminder to plan for communication and payment alternatives. For individuals, having a second payment method and offline access to essential information can help when a service is unavailable.
Products Worth Considering

Apple MacBook Air 13-inch with M5 Chip, 16GB Memory, 512GB SSD, Liquid Retina Display, and 12MP Center Stage Camera – Midnight

Bose TV Speaker Compact Soundbar with Bluetooth and HDMI-ARC, Black

DJI Mini 5 Pro Fly More Combo with DJI RC 2, 1-Inch CMOS
As an affiliate, we earn on qualifying purchases.
A Week of Separate Service Failures
The first incident began with Microsoft 365 on Nov. 12. Microsoft said the software change associated with a latent defect had begun deployment in July. Its preliminary account also described a gateway failover about 15 hours before the outage and reduced capacity from an unrelated earlier issue. Microsoft’s final report was due Nov. 20, according to the source material.
The FAA ground stop began at 3:53 p.m. Eastern on Nov. 13 and was canceled at 8:16 p.m., according to the times in the FAA advisory cited by the source. The outages at JPMorgan Chase, United, Apple and the NSA occurred early the following week. The source also reports that Microsoft 365 disruption affected organizations including Australia’s spy agency and federal police, the US House of Representatives, and the email support services of Indian airlines IndiGo and Akasa Air, citing Reuters.
As the events spread across prominent services, claims online framed them as a coordinated attack or a failure involving AI. The accounts provided do not substantiate either explanation. Microsoft explicitly described its outage as unrelated to cyber activity or AI agents; the other organizations gave their own causes, with varying levels of detail.
“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 to reporters in Manila
Investigations Still Lack Final Findings
No evidence of a link is not the same as a completed determination that the incidents could not be related. Rubio said officials had no indication connecting them, and the organizations named separate causes, but the source says only Microsoft had published a technical report as of Nov. 18—and that report was preliminary. The FAA account was also described as an initial investigation.
Technical details for the JPMorgan Chase, United Airlines and Apple outages were limited to brief descriptions. The source does not provide independent findings that verify each company’s account, nor details about the full scope or duration of those three disruptions. It also does not establish that patching caused any outage beyond the NSA incident; Clayton’s wider comments about institutions patching vulnerabilities were his general assessment, not a finding about the other failures.
Final Reports and Service Resilience
Microsoft’s final post-incident report was expected on Nov. 20, according to the material available on Nov. 18. The FAA’s investigation into the network flooding and work at the Amarillo and El Dorado sites remained ongoing. Further statements or technical findings from JPMorgan Chase, United, Apple and the NSA could clarify their incidents, but no dates for those updates were provided.
Until those findings arrive, the supported conclusion is limited: six outages occurred, organizations gave separate technical or maintenance explanations, and officials reported no evidence of a coordinated attack or link. The final causes, full effects and any broader connection remain unconfirmed.
Key Questions
Were the six outages caused by a coordinated cyberattack?
No evidence of a coordinated attack or link was reported in the source material. Rubio said officials had no reason to believe the incidents were related, and Microsoft said its outage was unrelated to cyber activity. Investigations were not all complete.
Which outage has the most detailed technical explanation?
Microsoft had published a preliminary technical report by Nov. 18. It cited a latent software defect, a gateway traffic shift and reduced server capacity as factors in the Microsoft 365 failure.
What caused the FAA ground stop?
The FAA said data flooded its network and 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 every reported flight disruption result from the ground stop?
No. The FAA said its Friday total of about 12,462 affected flights, including 9,082 cancellations by major airlines, was not entirely attributable to the ground stop.
What happens next?
Microsoft’s final report was due Nov. 20, and the FAA investigation remained underway. The source did not give publication dates for further technical findings from the other organizations.
Source: ThorstenMeyerAI.com
