Skip to content

Microsoft Outage: a Bug From July, Then FAA and Chase

Five US outages in four business days, from Microsoft 365 email to an FAA ground stop and slow Chase transactions. Every operator has now named a cause and none is a cyberattack. Each outage with the cause in the operator's own words, and what links them.

Đọc bản tiếng Việt →

Microsoft traced its 12 November outage to a software bug that had been running since July. The FAA blamed a router installation on an old network, and Chase a software bug in its own hardware. None of the operators named a cyberattack.

In four business days, from 12 to 17 November, the US had five large outages: Microsoft 365 email, the FAA's air traffic network, JPMorgan Chase transactions, then the NSA's internal communications and Apple services on the same day. Social media filled with theories about a coordinated attack. Below is each outage with the cause in the operator's own words, and what the pattern says.

Screenshot of the FAA's "Nationwide Ground Stop: Questions and Answers" page, dated 15 November 2026, with the answer to "What caused the outage?"

The week in one table

Date (ET)WhoWhat stoppedCause the operator gave
Thu 12 Nov, 11:20 a.m. to Fri 13 Nov, 11:10 a.m.Microsoft 365Outlook and Exchange Online email worldwide; Teams, OneDrive and SharePoint recovered earlierA latent bug in a July update to the networking gateway, triggered by extra load and reduced capacity
Fri 13 Nov, about 3:30 p.m. to 8:15 p.m.FAANationwide ground stop for departing flightsData flooding the FAA's telecom network, traced to two sites, one where contractor L3Harris was installing a new router
Mon 16 NovJPMorgan ChaseSome consumer transactions took longer than usual; transfers with other banks slowed"A software bug in on-premise hardware systems"
Tue 17 NovNSAInternal communications"Scheduled routine maintenance"
Tue 17 NovAppleSeveral products down or degraded"An internal update"

CNBC also reported a brief United Airlines outage on 16 November that delayed departures; no cause was given in that report.

Microsoft outage cause: a bug from July

Microsoft's preliminary post-incident review sits in the Microsoft 365 admin center, and Charles Lamanna, a Microsoft executive vice president, posted an abridged version on X on 16 November. Microsoft names three factors that combined:

  • A latent defect. A fix prepared for the Microsoft 365 networking gateway servers started rolling out in July. Under certain load, lock contention inside an internal process made servers stop responding. Microsoft says lab load tests missed it because they ran mostly on weaker hardware with fewer cores.
  • A surge in load. About 15 hours before the outage, Teams failed over from a second gateway to the primary one that also serves Exchange Online.
  • Less capacity. Nearly 14% of the gateway's servers were already out of service from an unrelated issue the day before.

When servers stopped responding, traffic was routed to the remaining ones, which then hit the same bug. Within two hours, more than 80% of the gateway servers were unresponsive, according to Microsoft. Teams, OneDrive, SharePoint and Office apps could move off the faulty gateway, which is why they came back first; Exchange Online could not. Recovery was slow because a bug that had been live for months could not be switched off with the usual rollback or feature flags. BleepingComputer, which read the admin-center report, puts the outage at nearly 24 hours, from 11:20 a.m. ET on 12 November to 11:10 a.m. ET on 13 November.

Was the Microsoft outage a cyber attack?

No, by Microsoft's account. Its report describes a software defect, a load shift and missing capacity. On 17 November, Director of National Intelligence Jay Clayton told CNBC the week's outages were not a cyberattack and not a coordinated effort by a nation state.

Where to check Microsoft outage status

Microsoft posts live incidents at status.cloud.microsoft and on its @MSFT365Status account on X. Admins of a Microsoft 365 tenant can read the full post-incident review in the Microsoft 365 admin center.

FAA ground stop: a router job on an old network

The FAA's question-and-answer page, dated 15 November, says its legacy equipment became unstable when data flooded the FAA Telecommunications Infrastructure (FTI) network at about 1,000 connection attempts every 4 to 5 seconds. Instability hit 17 of its 22 Air Route Traffic Control Centers. The initial investigation points to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris, the network provider, had been deploying a new router. Blocking those two sites stabilized the network.

The FAA says about 3,500 aircraft that were airborne landed safely, that it has no indication of a cyberattack, and that operators cancelled about 12,462 flights on 13 November, not all of them because of the ground stop. The FAA and L3Harris are still looking for the root cause.

Chase, the NSA and Apple

JPMorgan Chase told CNBC on 16 November that a temporary software bug in on-premise hardware slowed some transactions, that customers could still reach their accounts, and that there was "no evidence it is cyber-related". The bank said other banks were affected only when they were party to a transaction with Chase. On 17 November the NSA blamed scheduled routine maintenance and Apple an internal update.

What the pattern says

  • Each outage started with a routine change. A July update, a router swap, maintenance, an internal update. In Microsoft's case the change had run safely for over three months until load and capacity lined up.
  • Old systems spread the damage. The FAA blames its legacy TDM equipment, not the new routers. Microsoft's safeguards between regions did not stop the failure from cascading worldwide.
  • The timing looks connected, the causes do not. The five operators gave five unrelated technical causes. If you rely on Outlook, flights or online banking, the practical step is the boring one: know where each provider posts status, and have a second way to reach people and pay for things if one service is down for a day.

We kept to the causes the operators have published. The FAA's investigation is not finished, and Microsoft says a final post-incident review will follow. This summary is also in Vietnamese: Microsoft 365 bị lỗi, FAA, Chase.

FAQ

What caused the Microsoft outage on 12 November?

A bug in an update to Microsoft 365's networking gateway that began rolling out in July. A Teams failover added load, about 14% of gateway capacity was already offline, and the bug then made servers unresponsive one after another.

How long did the Microsoft 365 outage last?

About 24 hours for email: from 11:20 a.m. ET on 12 November until Microsoft confirmed full restoration at 11:10 a.m. ET on 13 November, according to BleepingComputer's reading of Microsoft's report.

Why did the FAA ground all flights on 13 November?

Its telecom network was flooded with connection attempts traced to two sites, including one where L3Harris was installing a new router. The FAA stopped departures from about 3:30 p.m. ET until 8:15 p.m. ET.

How this was made: an AI (Claude) collected the operator statements and news reports in the sources and wrote this summary. Every cause, time and figure was checked word for word against the FAA page, Microsoft's post on X, and the CNBC and BleepingComputer articles listed in the sources; nothing here is speculation about attacks.

Sources

  1. FAA: Nationwide Ground Stop, Questions and Answers (15 Nov 2026)

    Vendor page · Primary source

  2. Charles Lamanna (Microsoft EVP) on X: abridged preliminary post-incident review (16 Nov 2026)

    Vendor page

  3. CNBC: Widespread outages hit banks, air travel, the NSA and Apple (17 Nov 2026)

    Press

  4. CNBC: JPMorgan Chase says temporary software bug is affecting consumer banking (16 Nov 2026)

    Press

  5. BleepingComputer: Microsoft says months-old bug caused global Microsoft 365 outage (16 Nov 2026)

    Press