By Thorsten Meyer | November 18, 2026 | ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
One week, six outages. On Thursday, November 12, Microsoft 365 email stopped working for many of its business users. On Friday, the FAA stopped departures at every US airport. On Monday, JPMorgan Chase customers saw transactions stall, and United Airlines could not send its pilots the final weights they need for takeoff. On Tuesday, Apple’s iCloud and App Store faltered, and the National Security Agency’s classified internal network went down. By Tuesday evening, Secretary of State Marco Rubio was in Manila telling reporters: “we are not under systemic attack.”
Online, the six incidents quickly became one story: a coordinated attack, or AI gone wrong. The record so far tells a different one. Each organization has named its own cause, and none of them is an attacker. What the causes do have in common is less dramatic, and more useful to anyone who runs systems: every documented cause is a change that went wrong or a weak point that a change exposed. This piece lines up what each organization said, what is documented and what is only suspected, and what it means for businesses and for users.
All times are Eastern Time (ET), UTC−5, unless marked UTC or Pacific time (PT). Facts as of 13:30 UTC on Wednesday, November 18, 2026.
Key takeaways
- Six outages, six stated causes: Microsoft names a latent software defect introduced with a fix whose deployment started in July; the FAA names data flooding its network from router work at two remote sites; JPMorgan Chase names “a software bug in on-premise hardware systems”; United names “a technology issue”; Apple names “an internal update”; the NSA names “scheduled routine maintenance”, which Director of National Intelligence Jay Clayton tied to security patching.
- No evidence of an attack or a link, so far: every organization says it has no sign of a cyberattack. Rubio: “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.” That is a statement about the evidence today, not a finished investigation: only Microsoft has published a technical report so far, and it is preliminary.
- The common thread the evidence supports: changes to live systems (fixes, router installs, updates, patches), old infrastructure that new equipment has to work with, and single points that many people depend on at once: one mail gateway, one bank in the middle of many payments, one weight-and-balance system for an airline’s departures.
- The explanation officials offer: Clayton says “lots of institutions” are patching after newly found vulnerabilities, and that systems do not always come back as expected. He tied that directly to the NSA outage; for the others, it is his general reading, not a finding.
- What to do: businesses should treat changes to shared systems as risky work, know which vendors they cannot run without, and plan a fallback for payments and communication. Users should keep a second way to pay and an offline copy of anything they need on the day.
US tech outages · Nov 12–17, 2026
One week, six outages, six stated causes
Each dot is one outage, on the day it began, with the cause the organization itself gave.
- Microsoft 365Thu, Nov 12Latent software defect from a fix deployed since July, hit by extra load while nearly 14% of gateway capacity was out
- FAA ground stopFri, Nov 13Router traffic flooded legacy equipment: 1,000 connection attempts every 4 to 5 seconds
- JPMorgan ChaseMon, Nov 16“A software bug in on-premise hardware systems”
- United AirlinesMon, Nov 16“A technology issue”: no final weights for departing flights
- AppleTue, Nov 17“An internal update” took down iCloud, App Store and more
- NSA networkTue, Nov 17“Scheduled routine maintenance”; the DNI points to security patching
Sources: Microsoft preliminary post-incident report (Nov 15, 2026); FAA, “Nationwide Ground Stop: Questions and Answers” (revised, retrieved Nov 18); JPMorgan Chase statement to CNBC (Nov 16); United Airlines statements and pilots’ union memo, via CBS News (Nov 16); Apple statement to CNET and Variety and Apple system status (Nov 17); NSA statement and DNI Jay Clayton, via CNN and Fox Business (Nov 17); US Department of State, Rubio remarks (Nov 17).
Graphic: Powered by Thorsten Meyer AI
Products Worth Considering

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)

Apple Watch Series 12 GPS 42mm Smartwatch

Apple MacBook Air 15-inch Laptop with M5 Chip, 24GB Memory, 1TB SSD, Midnight
As an affiliate, we earn on qualifying purchases.
The week, outage by outage
Thursday, November 12: Microsoft 365
Many business users could not reach their Exchange Online mailboxes, and everything that depends on them went with it: Teams calendars, parts of SharePoint, Microsoft 365 Copilot and more. Microsoft’s final status gives 16:20 UTC on November 12 to 16:10 UTC on November 13, 23 hours and 50 minutes. On Friday, it called the incident “a technical issue not related to cyber or AI / agents”.
Stated cause. Microsoft’s preliminary post-incident report, dated November 15, names three factors. First, “a latent defect caused Windows servers to become overwhelmed and unresponsive under certain load conditions”; the change behind it “first started deployment in July of this year”. Second, “Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online.” Third, “nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day.” Traffic moved to the remaining servers, which caused “a cascading failure from server to server”; “At its lowest, more than 80% of servers were unresponsive.” The final report is due on November 20.
The ripple. According to Reuters, Australia’s spy agency and federal police were among the organizations caught up in the outage, and the US House of Representatives said it affected its users. Indian airlines IndiGo and Akasa Air said their email support services were impacted, Reuters reported. The full timeline is in our Microsoft 365 outage article.
Friday, November 13: the FAA ground stop
From 3:53 p.m. ET (20:53 UTC), by the event time in its advisory, the FAA’s Command Center ground-stopped all US airports: “ALL AIRPORTS ARE GROUND STOPPED.” The cancellation took effect at 8:16 p.m. ET (01:16 UTC), 4 hours and 23 minutes later (our arithmetic). BBC News called it “the longest nationwide ground stop of flights since the 11 September 2001 attacks”. Nearly 25,000 flights were delayed and over 9,000 cancelled on Friday, according to FlightAware as reported by NPR; on Saturday morning, more than 4,000 cancellations had been recorded, “which is 18% of flights departing the U.S.”, according to data from the aviation analytics company Cirium, NPR reported. The FAA’s own count for Friday is “approximately 12,462 flights, including 9,082 cancellations by major airlines”, not all of them directly caused by the ground stop.
Stated cause. The FAA’s written account: “The FAA’s legacy equipment became unstable when data began flooding the FAA FTI network, at a rate of 1,000 connection attempts every 4 to 5 seconds.” Its initial investigation points to two sites, a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where the contractor L3Harris had been deploying a new router. In its revised account, the FAA writes that it disabled “the functionality of the originating Juniper routers”, did the same “on more than 60 other Juniper routers in the system”, “and we have paused installing them.” It says: “Based on all available evidence, we have no indication that this was a cyberattack or an outside nefarious actor.” The root cause is still under investigation.
Copper and fiber. On Saturday, Transportation Secretary Sean Duffy said the contractor was doing “routine maintenance to switch telecommunication lines from old copper wire” to fiber at a remote site, according to Fox Business. The FAA’s written account does not tie the router to that work directly; it says that “This type of work has been going on for years to transition from old copper wires that are being disconnected due to their obsolescence.” L3Harris says it has completed “more than 70% of the planned airspace communications conversion from legacy copper wires to a fiber optic system”. The details are in our FAA ground stop article.
Monday, November 16: JPMorgan Chase
Users reported errors from about 11:30 a.m. ET, according to CNBC. Customers of other banks were listed in outage reports too, and U.S. Bank said clients sending or receiving Zelle payments with another bank “may experience transaction delays”.
Stated cause. The bank said a “temporary issue related to a software bug in on-premise hardware systems” was making some customer transactions take longer than usual, and that customers could still access their accounts and funds, CNBC reported. “There is no evidence it is cyber-related,” a JPMorgan spokesperson told CNBC. “This is not a systemic issue — other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us.” A Chase spokesperson told Newsweek that transactions were posting normally as of Monday evening. The bank has not said what the bug was.
Monday, November 16: United Airlines
Just before 5 p.m. ET, United said it was dealing with a widespread system outage affecting departing flights; about an hour later it said: “We have resolved a technology issue that delayed flight departures.” And: “While some flights were delayed, there was no impact on flights in progress, or on United Express flights.” According to CBS News, the outage lasted about 90 minutes; a United spokesperson told CNN it lasted about 30 minutes, with fewer than 150 flights impacted. Departures were delayed; the FAA told CNN “it’s not an FAA equipment issue.”
What broke. A memo from the union representing United’s pilots pointed to the weight and balance calculation system: “The Company cannot provide outbound flights with final weights,” according to CBS News. According to an internal company alert obtained by CNN, affected applications included flight planning, weather briefing and crew management tools. A United spokesperson said there was no indication of a cybersecurity issue. United has not named a cause beyond “a technology issue”.
Tuesday, November 17: Apple
Apple’s system status page lists iCloud Account & Sign In, iCloud Mail and iCloud.com as slow or unavailable for some users from 08:45 to 13:15 PT, the App Store with an outage from 08:45 to 12:00 PT, and AppleCare purchases on devices “temporarily unavailable” from 08:15 to 12:39 PT, when “All users were affected”. Apple Pay drew a spike of user reports on Downdetector, according to CNET; Apple’s status page, as we retrieved it on Wednesday, lists no Apple Pay event.
Stated cause. “Many of our systems are back up and running after an internal update caused some outages this morning,” an Apple spokesperson told CNET. The outages were not caused by a cyberattack, a person familiar with the matter told Variety. Apple has not said what the update was.
Tuesday, November 17: the NSA
NSANet, the network NSA employees use to share classified information internally, went down, according to CNN, which first reported it citing six people familiar with the matter. The agency said in a statement: “The National Security Agency experienced temporary degradation during scheduled routine maintenance.” And: “While some internal systems were affected, mission-critical capabilities remain fully operational and our ability to defend national security continues.”
Stated cause. Clayton said on Fox Business: “The patching that has gone on following that has caused some of these systems to not come back up when you patch them as expected,” according to CNN, and: “That is what has happened at the NSA today.” According to CNN, he was referring to vulnerabilities in the programming language PHP discovered last month. On Tuesday night, the NSA closed its campus to most employees and kept essential personnel only while it worked to restore the network, CNN reported; a source told CNN restoration was ongoing but not yet complete.

Documented versus suspected
Documented, by the organizations themselves: a software defect at Microsoft, router traffic flooding legacy equipment at the FAA, a software bug at JPMorgan Chase, an internal update at Apple, and maintenance at the NSA. Each organization says it sees no sign of an attack. Only Microsoft has published a technical report, and it calls its own findings preliminary.
Said by officials, across the board: “This is not cyberattack, and this is not a coordinated effort by a nation state,” Clayton told CNBC. “We’ve looked very closely.” Homeland Security Secretary Markwayne Mullin said on Fox News’ “Hannity”: “I can tell you with 98% certainty we’re not seeing the cyberattack.” And: “We’re not seeing the footprints going in. We’re not seeing the footprints going out,” he said. Rubio, in his State Department transcript, said the incidents are “completely unrelated one from another” and that “every indicator we have is that every single one of these events has an explanation or a cause that has nothing to do with a cybercriminal, has nothing to do with a hostile actor or another country.”
Suspected, without evidence: a coordinated attack. “Our leaders are lying to us. This is very clearly a coordinated cyberattack,” the right-wing personality Laura Loomer wrote on X; she did not present any evidence of an attack, AP notes. Suggested, without evidence: AI. Mullin said a technology expert had told him that “super intelligence” could have contributed, a theory he said “kind of makes sense”; he offered no evidence. Asked about AI, Rubio said: “I don’t want to speculate on it because, again, every one of these instances is distinct and unique.”

The patching explanation
The explanation officials keep returning to is ordinary work done in a hurry. “Lots of institutions, because these vulnerabilities have been identified, are patching. They’re taking their systems down. They’re upgrading them. They’re putting patches in place,” Clayton said on Fox Business. “Some systems have to hand off to other systems, and those handoffs are not coming as expected.” Rubio described it the same way: “sometimes when you are going in to fix your system because you’ve identified a vulnerability, it creates a short-term disruption in the way your system works. That’s how – that’s how it’s been described to me.”
Senator Mark Warner, vice chair of the Senate Intelligence Committee, said there is no indication the incidents are the result of an attack, and pointed to AI as a source of pressure: “AI is making it possible to identify vulnerabilities across enormous numbers of systems at unprecedented speed, creating enormous pressure on companies and government agencies to patch those vulnerabilities immediately, often all at once, putting tremendous strain on systems that weren’t built to handle that pace of change,” he wrote on X, according to CBS News.
This is a plausible reading, not a documented one. Clayton tied patching to the NSA outage specifically. Microsoft’s defect came from a change deployed months earlier, the FAA’s from router work, and Chase, United and Apple have not said whether a security patch was involved.
The politics
President Donald Trump, asked in Manila about the Chase outage: “It’s life. When you’re big and powerful and you have all the money, things like that happen. It’s fine,” AP reported. Critics, including some of his allies, asked for more. “What I would say to the White House is: transparency is key,” Karoline Leavitt, Trump’s former press secretary, said on Fox News, according to AP. “Americans aren’t stupid,” Tricia McLaughlin, a former DHS spokesperson, posted. “We want and deserve to know what’s really going on.” Meghan McCain wrote on X: “No one who lived through COVID is believing this is all a coincidence.” House Democratic Leader Hakeem Jeffries said “it’s time for the administration to come up to the Hill and explain themselves”, according to CNBC.
The agency that would usually help companies respond, CISA, is smaller than it was. In an August letter to the Government Accountability Office, five House Democrats wrote that CISA “has lost nearly one-third of its workforce”. Government Executive reported at the time that staffing had fallen from roughly 3,300 employees to about 2,200 and that Mullin had said CISA may need roughly 600 additional staff. No official has linked the staffing to this week’s outages.
The common thread
Nothing in the record links the six outages to one cause. They do share a pattern, and each part of it is documented in at least one case:
- Change is the trigger. Microsoft’s defect arrived with a fix; the FAA’s flood followed router work; Apple names an internal update; the NSA names maintenance and patching. Most outages do not start with something breaking on its own, but with someone changing something that works.
- Old and new have to work together. The FAA says its “legacy equipment” became unstable. Microsoft’s report says its load tests “tended to focus on weaker hardware with fewer cores”, while the defect was worse on newer machines with more cores. Mixed estates fail at the seams.
- Redundancy can spread a failure. At Microsoft, redirecting traffic to healthy servers, which normally keeps the service up, spread the defect from server to server. At the FAA, one router’s traffic reached 17 of 22 en route centers.
- Many people depend on a few systems. One mail gateway carried email, calendars and AI connectors for much of the business world. Other banks’ customers felt Chase’s bug because they were sending money to or from Chase. One airline system held up departures across United’s network.
What it means for businesses
- Treat changes to shared systems as the risky part. Schedule them for quiet hours, roll them out in stages, test them on the hardware you actually run, and know how to roll back. The FAA itself says it “will reevaluate when we do replacement/maintenance work”.
- Map your single points of failure. Which one provider, if it goes down for a day, stops your email, your calendar, your payments or your AI workflows? Microsoft’s outage reached AI connectors at OpenAI and Anthropic; United’s reached the weights pilots need before takeoff.
- Plan the fallback for payments and communication. A second payment processor or bank account, a way to reach staff and customers outside your main mail system, and printed or offline copies of the procedures you need when the screens are blank. United’s pilots were told to follow their flight operations manual, according to NBC News.
- Patch, but patch with a plan. Officials’ advice amounts to a trade-off: unpatched systems invite attackers, and rushed patches cause outages. The answer is a patch process with staging and a rollback, not skipping patches.
- Communicate early. In every case this week, the first official statement shaped what people believed. Say what is known, what is ruled out and what is not known yet, and update it.
What it means for users
- Keep a second way to pay. A card from a different bank, and some cash, cover a day when one bank’s app or one payment service stalls.
- Keep offline copies. Boarding passes, tickets, confirmation numbers and important documents, saved on the device or printed, not only behind a sign-in.
- Check your transactions afterwards. After a delay, payments can arrive late or in a burst. Check that nothing went through twice before you send it again.
- Be wary of “fix” messages. Outages bring scam texts and emails that offer refunds or ask you to sign in again. Use the company’s own app or website.
What is not known
- The root causes, in full. Microsoft’s final report is due on November 20. The FAA and L3Harris are still investigating. JPMorgan Chase, United and Apple have not described their faults beyond one line each.
- Whether the NSA network is fully back. On Tuesday night, CNN reported that restoration was still ongoing.
- How far the patching explanation reaches. Clayton tied it to the NSA; whether security patches played a role anywhere else has not been said.
- How many people were affected. None of the organizations has published a count of affected customers; Downdetector figures are user reports, not affected users.
- Whether a link will turn up. Officials say there is no evidence of one today. Investigations are not finished, and evidence can change.
The bottom line
The week looked like a pattern, and in one sense it was: not an attack, according to everyone who has spoken on the record, but a run of changes to complex, interconnected systems that did not go as planned. That is less frightening than a cyberattack and harder to fix, because the cure for it is not a single patch but slower, better-tested change, and fallbacks for the days it still goes wrong.
Further reading: our Microsoft 365 outage timeline, what failed in the FAA ground stop, and last week’s outages and breaches side by side.
I’m Thorsten Meyer. The full sources are below, and more reality checks are at thorstenmeyerai.com.
Sources
- US Department of State: “Secretary of State Marco Rubio”, remarks to the press, Manila, Philippines, state.gov (retrieved 12:52 UTC, November 18, 2026)
- Microsoft: “Preliminary Post Incident Report for Microsoft 365”, EX1550543/MO1550821, report date November 15, 2026, as published by 365Fanatic (retrieved November 17, 2026); Microsoft service health final status EX1550543, as mirrored by Cloud Admin Hub (retrieved November 17, 2026); Microsoft 365 status page, update of 17:57 UTC, November 13, 2026
- FAA: “Nationwide Ground Stop: Questions and Answers”, faa.gov, November 15, 2026, revised version retrieved 08:59 UTC, November 18, 2026
- L3Harris: “L3Harris Statement on the Nov. 13 Ground Stop”, l3harris.com (retrieved 09:00 UTC, November 18, 2026)
- Apple: System Status, apple.com/support/systemstatus (data retrieved 12:49 UTC, November 18, 2026)
- CNBC: “JPMorgan Chase says temporary software bug is affecting consumer banking”, November 16, 2026
- CNBC: “Widespread outages hit banks, air travel, the NSA and Apple, disrupting seemingly everything”, November 17, 2026
- CBS News: “United Airlines says it resolved a ‘widespread system outage,’ days after nationwide ground stop”, November 16, 2026
- CNN: United Airlines outage report, November 16, 2026
- NBC News: “United Airlines says it has resolved a ‘widespread system outage'”, November 16, 2026
- CNN: “Exclusive: Highly classified US national security communications network goes down, sources say”, November 17, 2026
- The Record: “NSA Net, agency’s classified internal network, faces unspecified disruptions”, November 17, 2026
- NBC News: “Classified NSA network went down, but no indication it was an attack, sources say”, November 17, 2026
- Fox Business: “Jay Clayton says no cyberattack behind tech outages”, November 17, 2026
- CNET: “Apple Reports Outage Affecting Some Services”, November 17, 2026
- Variety: “Apple Hit With Outages in iCloud, Apple Pay and More Services”, November 17, 2026
- AP, via KSAT: “Rubio says there’s ‘zero’ information that US outages are linked or caused by a malign actor”, November 17, 2026
- CBS News: “Rubio says there’s ‘zero evidence’ recent tech outages are related”, November 18, 2026 (including Sen. Mark Warner’s post on X)
- Fox News: “DHS chief says FAA, Microsoft, bank outages were ‘unrelated,’ not cyberattacks”, November 16, 2026
- Newsweek: “Trump Says He’s Not Worried About Outages Affecting Banks, FAA: ‘It’s Life'”, November 17, 2026
- NPR: FAA ground stop coverage of November 14, 2026 (FlightAware and Cirium figures)
- BBC News (via AOL): “What we know about the US ground stop and what to do if your flight is affected”, November 14, 2026
- Fox Business: “Sean Duffy says L3Harris work may have caused FAA nationwide ground stop”, November 14, 2026
- FAA Air Traffic Control System Command Center: advisories 111 of November 13 and 005 of November 14, 2026 (UTC dates), fly.faa.gov (retrieved November 14, 2026)
- Reuters, via The Korea Times and Rappler: Microsoft outage coverage, November 13, 2026
- Reps. James Walkinshaw, Delia Ramirez, Bennie Thompson, Seth Magaziner and LaMonica McIver: letter to the Government Accountability Office on CISA staffing, August 20, 2026, page 1
- Government Executive: “House Democrats want answers on what CISA lost in workforce cuts”, August 2026
Researched and drafted with AI assistance, including Anthropic’s Claude. Anthropic is named in this article because its product was affected by the Microsoft outage; no company, agency or official named here reviewed or sponsored this article. Our own text and graphics contain no affiliate links; offer and product boxes added by the site may contain Amazon affiliate links. This article is for information only; it is not financial, legal or security advice. Statements as published by the organizations named and as reported by the outlets above, as of 13:30 UTC on November 18, 2026. Images: AI-generated illustration (Runware) and graphics by Thorsten Meyer AI; our own images show no real people or logos. Boxes added by the site may show product photos or people.
