🔍 Read the full analysis: A Guide To The Week Of US Tech Outages Affecting Banks, Flights, Email, And The NSA on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Between Nov. 12 and 17, outages affected Microsoft 365, U.S. air travel, JPMorgan Chase, United Airlines, Apple services and an NSA network, according to a Nov. 18 account by ThorstenMeyerAI.com. The organizations named separate technical or maintenance causes, and officials said they had no evidence the events were linked or the result of attacks; several explanations and investigations remain incomplete.
The first incident began on **Thursday, Nov. 12**, when many business users could not access Microsoft 365 email and related services. Microsoft’s status record put the disruption at **23 hours and 50 minutes**, ending at 16:10 UTC on Nov. 13. Its preliminary report, dated Nov. 15, said a latent software defect could make Windows servers unresponsive under certain loads. Deployment of the change behind the defect had started in July, Microsoft said.
Microsoft also identified a network failover and reduced capacity as contributing conditions. Teams moved from an alternative gateway to a primary gateway also supporting Exchange Online, while nearly **14% of gateway server capacity** was already unavailable. Microsoft said the resulting traffic surge led to a cascading failure; at the worst point, more than 80% of servers were unresponsive. The company’s final report was due Nov. 20.
On Friday, Nov. 13, the Federal Aviation Administration issued a nationwide ground stop. Its written account said legacy equipment became unstable as data flooded its FAA Telecommunications Infrastructure network, with **1,000 connection attempts every four to five seconds**. The FAA’s initial investigation pointed to router work at a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas. The FAA counted approximately **12,462 flights affected Friday, including 9,082 cancellations by major airlines**; that total was not limited to flights directly caused by the ground stop.
Further disruptions followed on Monday and Tuesday. JPMorgan Chase said a software bug in on-premise hardware systems affected customer transactions; United Airlines described a technology issue that prevented delivery of final aircraft weight figures to pilots. Apple attributed problems affecting iCloud and the App Store to an internal update. The NSA said its classified internal network outage followed scheduled routine maintenance. Director of National Intelligence Jay Clayton connected that incident to security patching. These explanations are the organizations’ stated accounts, not independent technical findings.
The incidents affected services that many people and organizations depend on at the same time. An email outage can also disrupt calendars, collaboration tools and customer support; the flight ground stop and airline technology problem affected travel operations; a bank systems issue can interrupt payments. The week showed how a fault in a shared gateway, legacy network or operational system can reach users well beyond the equipment where the problem began.
The report’s supported common thread is not a single cause, but **changes to live systems and vulnerabilities exposed during those changes**. Software fixes, router installations, internal updates and security patches can interact with older equipment or reduced backup capacity. That is a practical risk for operators to manage, but it does not establish that the separate outages had a common technical origin.
For customers, the immediate consequence is that access to essential services can fail even when there is no evidence of an attack. The report recommends that businesses plan alternatives for communications and payments and understand their dependence on vendors. Users may want a second payment method and offline copies of information needed during travel or work. These are precautions, not evidence that further outages are expected.
Products Worth Considering

Bose QuietComfort Wireless Noise-Cancelling Headphones, Moonlight Grey

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

Logitech MX Brio Ultra HD 4K Webcam
As an affiliate, we earn on qualifying purchases.
A Week of Separate Disruptions
The account by ThorstenMeyerAI.com, dated **Nov. 18, 2026**, describes six incidents across five days. Microsoft’s outage began Nov. 12 and continued into Nov. 13; the FAA ground stop occurred Nov. 13; banking and airline disruptions were reported Monday; and Apple and NSA outages followed Tuesday. The incidents quickly prompted speculation online that they reflected a coordinated attack or an AI-related failure.
The available explanations differ. Microsoft published a preliminary technical report, while the other causes in the account are short descriptions from the affected organizations or officials. The report also cites outside reporting on the consequences: Reuters said Australian federal agencies and U.S. House users were among those affected by the Microsoft outage. NPR reported FlightAware data showing nearly 25,000 delays and more than 9,000 cancellations on Friday; the FAA’s separate total was approximately 12,462 affected flights, including 9,082 cancellations by major airlines. The counts use different sources and should not be treated as interchangeable.
““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.””
— U.S. Secretary of State Marco Rubio, speaking to reporters in Manila on Tuesday, according to ThorstenMeyerAI.com
Investigations Have Not Finished
There is **no public evidence in the source account that the six incidents were coordinated**, but the lack of evidence so far is not proof that all possible links have been ruled out. Rubio said officials had no reason to believe the events were related. The account does not describe a completed cross-agency investigation or a shared technical review.
Only Microsoft had published a technical report by the stated cutoff of **13:30 UTC on Nov. 18**, and that report was preliminary. The final report was expected Nov. 20. The FAA’s account described its investigation as initial. For JPMorgan Chase, United, Apple and the NSA, the reported explanations were brief; the account provides no comparable technical post-incident reports or detailed timelines. It remains unclear whether further findings will change or expand those explanations.
Jay Clayton said institutions were patching systems after newly discovered vulnerabilities and that systems do not always restart as expected. He tied that explanation specifically to the NSA outage; for the other incidents, it was his general interpretation, not a confirmed shared cause. The available information also does not establish that AI systems played a role in any of the outages.
Reports and Agency Reviews Ahead
Microsoft’s final post-incident report was due **Nov. 20**, according to the account. It may provide more detail on the defect, the network failover and capacity loss, and the sequence that produced the cascading server failure. The FAA and the other affected organizations may also release additional findings, but no publication dates for their reports were provided.
Until more information is released, the reported causes should be treated as separate organizational accounts rather than a single explanation for the week. Readers should watch for updated technical findings, revised impact figures and any official evidence that changes the current assessment of whether the incidents were connected. As of the Nov. 18 cutoff, officials said they had **no evidence of a coordinated attack or link**.
Key Questions
Were the six outages caused by one cyberattack?
No evidence of a common attack had been reported by the Nov. 18 cutoff. Rubio said officials had no indication or reason to believe the incidents were related. Investigations were not all complete.
What caused the Microsoft 365 outage?
Microsoft’s preliminary report cited a latent software defect, a failover to a gateway also serving Exchange Online, and nearly 14% of gateway capacity being unavailable. Microsoft said the combination triggered cascading server failures.
Why were U.S. flights disrupted?
The FAA said legacy equipment became unstable as data flooded its network. Its initial investigation pointed to two sites where router work was under way. The agency reported approximately 12,462 affected flights on Friday, including 9,082 cancellations by major airlines.
Did AI cause the outages?
The source account provides no evidence that AI caused any of the incidents. Microsoft said its outage was not related to cyber activity or AI agents. The other reported causes involved software, network equipment, internal updates or maintenance.
What is still expected?
Microsoft’s final report was due Nov. 20, 2026. The account gave no set dates for further FAA or company reports, and said several investigations remained incomplete.
Source: ThorstenMeyerAI.com
