Geopolitics Alpha

Market closed · last trade · ETF proxies, Alpaca IEX

Analysis

Six U.S. Outages in Six Days: What Officials Have Said, and What Is Still Unexplained

Published . Updated .

At 3:30 p.m. Eastern on Friday, Nov. 13, the FAA halted takeoffs across the United States. About 3,500 aircraft were already in the air. Every one of them landed.

It was the second major U.S. outage in two days. A Microsoft 365 failure had already stretched from Thursday morning into Friday. By Tuesday, Chase, United, Apple and a classified NSA network had gone down too.

No cyberattack has been confirmed.

Three of the six have a primary official account: Microsoft, the FAA, and Chase. Each describes a software bug, a botched change, or another technical cause, and each names a different system. For United, a secondary report said a cyberattack was ruled out; we have not found a statement from the airline itself. Apple and NSA causes appear in coverage, not in primary documents retrieved for this review.

When (ET)SystemOfficial or reported causeStatus
Nov. 12, 11:20 a.m.–Nov. 13, 11:10 a.m.Microsoft 365Gateway defect dormant since July, exposed by a traffic shift, with the fleet already below capacityConfirmed. Microsoft: not cyber or AI
Nov. 13, ~3:30–8:15 p.m.FAA ground stopNew router work by L3Harris at El Dorado, Ark., and data flooding that also involved an Amarillo, Texas, radar siteConfirmed. FAA: no indication of a cyberattack; root-cause review continues
Nov. 16, ~9:30–11:30 a.m.ChaseSoftware bug in on-premise systems; other banks lit up on outage maps because of Chase transfersConfirmed. Chase: not cyber-related
Nov. 16, ~5:20 p.m.UnitedBrief "widespread system outage." A Jerusalem Post headline said cyber was ruled outReported. No primary United statement found
Nov. 17, from ~11:15 a.m.Apple (Pay, iCloud, App Store)Reports describe an internal updateReported as not cyber; no primary Apple statement in this review
Nov. 17NSA classified networkScheduled maintenance; scope undisclosedReported. No cyber reported; NSA.gov statement not independently retrieved

Six days, and the weeks before

Big outages show up in our news archive about every week or two: an FAA cable problem in Newark/Philadelphia in late September, a Google Cloud power event in London in October, PHP-patch failures, a CSX incident, a Japanese bank system. Six in six days is unusual.

From mid-October through Nov. 8, outage stories were about 0.1% of the articles in our database. By Nov. 16–18 they were about 0.91%, roughly eight times the earlier share, much of it follow-up coverage of the same failures.

Microsoft and the FAA, on the record

Microsoft has published a preliminary post-incident account, described in detail by Ars Technica. Confirmed: a change to the cloud gateway, rolled out from July, left a latent bug that could exhaust CPU and memory. Ordinary traffic shifts during network maintenance exposed it. The gateway fleet was already running at 14% below optimal capacity, so there was little spare room when requests piled up.

Microsoft places the outage between Nov. 12 at 16:20 UTC and Nov. 13 at 16:10 UTC and lists the final status as "a technical issue not related to cyber or AI/agents."

The FAA's questions-and-answers page, posted Nov. 15, is specific. Confirmed: a technical problem at about 3:30 p.m. ET on Nov. 13 triggered a nationwide ground stop "out of an abundance of caution." Air traffic resumed at 8:15 p.m. the same day.

The initial investigation points to excessive data flooding the system, with two sites in view: a radar facility in Amarillo and a radio site in El Dorado, where L3Harris, the FAA's network provider, had been deploying a new router. The agency said it disabled the originating Juniper routers, disabled the same function on more than 60 others, and paused further installs.

Asked whether this was a cyberattack, the FAA said that based on all available evidence, it has "no indication that this was a cyberattack or an outside nefarious actor." It also said the FAA and L3Harris continue to investigate the root cause.

Operators canceled about 12,462 flights that day, including 9,082 at major airlines. The FAA notes that not all of those cancellations were caused directly by the ground stop.

Chase, United, Apple, the NSA

On Nov. 16, Chase customers lost service for about two hours. Confirmed, from the bank's comments in our bank-outage report: a software bug might be causing the issue, and it was not "systemic" or "cyber-related." Other banks appeared on outage trackers because transfers that pass through Chase failed.

United halted flights that evening for a short "widespread system outage," two days after the FAA stop and just before the Thanksgiving rush, as our United report noted. Reported: the only cause on file is a Jerusalem Post headline saying cyber was ruled out. No primary United statement has been found.

Apple dealt with outages affecting Apple Pay, iCloud and apps on Nov. 17. Reported: coverage describes an internal update, not a breach. We have not independently retrieved a primary Apple statement.

The same day's NSA story points to scheduled maintenance on a classified communications network, with no cyberattack reported and the scope undisclosed. Reported: we were not able to retrieve the agency's own press page in this review.

The six events do not share a publicly identified vendor, attacker, or method. Several began with a change the operator or a vendor was making.

A separate cyber campaign in Europe has hit food cold chains and, this week, the IT systems of an energy major; our Desk analysis of Europe's cold-chain attacks covers it.

What the stocks did

The sharpest moves were at companies that had the outage. United fell 4.0% the day of its own failure, with the U.S. Global Jets ETF down 2.3%. After the FAA stop, United was down 2.6% that session, the iShares U.S. Aerospace & Defense ETF was down 2.7%, and Boeing fell 4.4% the next day.

JPMorgan dropped 4.7% the session after the Chase incident. Wells Fargo fell 3.9%, and the Financial Select Sector SPDR was down 2.5%.

The Microsoft window overlapped a chip selloff and inflation data. The Technology Select Sector SPDR was down 5.3% the next day and 6.0% two days later. Salesforce fell 10.6% and Oracle 9.5% at the two-day mark.

What to watch

Watch the post-incident paper, and the wider argument about fragile systems: Microsoft's chief has warned that A.I. makes more tech outages likely. The documents that would fill the gaps, or change the public record, are a CISA or FBI finding, or a final company report, that any of the six was malicious; evidence of a shared vendor or supply-chain implant; or a credible claim that ties one of these failures to a known campaign.

The names that already moved on their own outages are United, JPMorgan, and Microsoft, plus the airline, bank and tech sector ETFs (JETS, XLF, XLK) if another core system fails.

The next document that matters is not another outage map. It is a report from United, Apple or the NSA that explains what broke — or a finding from CISA or the FBI.


*This article is for informational purposes and is not investment advice. Official causes can be revised. Stock moves are stored closing-price reactions after each story, measured as described in our methodology, and are confounded by the broader market.*

Sources