NY
Closed
LDN
Closed
TKY
Closed
Calendar
Contact
Markets now

PolicyMarket note

Three US outages in four days, and no attack: what grounded the planes and slowed banks

The FAA ground stop, United’s outage and Chase’s payment bug came in four days. Officials found no attack: a router, a tech fault and a bug.

By The Notebook Desk

The tall concrete air traffic control tower at John F. Kennedy International Airport, rising behind a curved terminal roof under a grey sky
Photo: Eheik, via Wikimedia Commons, public domain. Pixels by The Macro Notebook.
In this item4 parts
  1. What grounded the planes?
  2. What happened at United and JPMorgan?
  3. Was it an attack?
  4. Why does it matter for markets?

In four days, three systems that America runs on stopped working. On Friday the Federal Aviation Administration stopped departures across the country. On Monday United Airlines held its departing flights, and JPMorgan Chase slowed payments that reached other banks. Every official account says the opposite: there is no evidence of an attack in any of the three. A router, on the FAA’s first findings, a technology fault and a software bug did it, and that is the more worrying finding.

An attack has an attacker, who can be found and stopped. A system that fails on its own can fail again for the same reason: old equipment, a change made in the middle of the working day, a bug no one caught. This week showed how little it takes to stop flights for a nation and payments for millions of people, at a time when the Federal Reserve’s own survey of the markets ranks attacks on payment systems among the gravest risks they face.

What grounded the planes?

Most likely a router, Duffy says. At 3:36 p.m. Eastern time on Friday 13 November, the FAA “experienced telecommunications issues at facilities & TRACONs across the country”, Transportation Secretary Sean Duffy said on X. The agency stopped departures nationwide, letting only critical flights such as medevac and law enforcement continue, while more than 3,500 aircraft were in the air, and lifted the stop at 8:15 p.m. Every flight landed safely.

The FAA’s account, published on Sunday, is unusually frank. Its “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”. The flood unsettled aircraft communications and radar feeds, and instability began at 17 of its 22 en-route control centres, which handle planes between airports. The first investigation points to two sites, a radar in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris, the FAA’s network contractor, had been installing a new router. When L3Harris blocked the two sites, the network settled.

The cost landed on passengers. Airlines cancelled about 12,462 flights that Friday, the FAA says, though not all of them because of the stop. United cancelled “a significant number” of evening flights and warned of disruption into the weekend, its statements show.

The FAA admits the timing was wrong. Maintenance at big facilities is normally done at night; the work in Arkansas was a routine replacement done by day, and “based on what happened Friday, we will reevaluate when we do replacement/maintenance work”, it says. On the cause it is firmer: it has “no indication that this was a cyberattack or an outside nefarious actor”. Duffy said the FBI is still part of the investigation, and that the two routers are being tested at L3Harris in Florida, with engineers from Juniper and Cisco, he posted on Sunday. On Monday he called the router “the likely cause of Friday’s nationwide ground stop”, in another post.

Washington has drawn a political lesson from it. The ground stop “happened because our air traffic control system is operating on DECADES-OLD, analog equipment”, Duffy wrote, asking Congress for money beyond the $12.5bn “down payment” already secured. President Trump said “we have old equipment, broken equipment”, the White House posted. Scott Kirby, who leads United, called it “a call to action” in a letter on Sunday: the air traffic system “needs more investment in modern technology to ensure better redundancy and reliability now”. The FAA says its upgrades did not cause the failure: the instability came from its legacy system.

What happened at United and JPMorgan?

Two failures came on Monday, and no one has linked either to the FAA’s. United said it was “troubleshooting a technology issue affecting departing flights”, with no effect on flights already in the air, it posted, and later that evening that “the issue has been resolved”, it told a customer. It has not said what failed or how many flights were held.

JPMorgan Chase was more specific. It had “a temporary issue related to a software bug in on-premise hardware systems – there is no evidence this is cyber-related”, the bank said on X. Some customers were served more slowly, and “where we were party to a transaction involving other banks, those banks may have been impacted, but this is not a systemic issue”. Customers kept access to their accounts and money, it said, and it aimed to fix the fault by the end of the day.

That last point is how one bank’s bug became other banks’ problem. A payment has two sides, and when Chase’s side slowed, the bank on the other side waited too. To its customers, the delay could look like a fault at their own bank.

Was it an attack?

No, on everything officials have said. The FAA and Duffy say there is no sign of a cyberattack on the air traffic network; Chase says there is no evidence of one at the bank; and Mullin, the Homeland Security Secretary, said on Monday that “the homeland is secure. Our banking system is secure. And when something like this happens, we’re able to react—and react fast”, in a clip the White House posted. No official has said the three events are linked: each body has described only its own failure.

That does not make the fear foolish. The Federal Reserve’s Financial Stability Report, published last Friday, says the market contacts the New York Fed surveyed saw cyberattacks on financial infrastructure as a growing risk, and that “disruptions to trading, settlement, or payment systems could materially damage confidence in financial institutions”. Google’s threat researchers said on Monday that attackers now use AI to find newly patched flaws and build attacks “without human involvement”, and that “defending against machine-speed threats at human speed isn’t feasible”, in their latest report. Michael Barr, a Fed governor, put it bluntly in a speech in Milan the same day: “Attackers only need to be right once, while defenders need to be right all the time.”

Why does it matter for markets?

Our view: this week was a stress test that nobody planned, and the systems passed on safety and failed on resilience. Every plane landed, and Chase says its customers kept access to their money. But the likely cause of the ground stop was a router at a remote site, and departures across the country stopped for more than four and a half hours; one bug at one bank slowed payments at others. Neither needed an attacker.

The bill will come in two forms. The first is public: Congress is being asked to pay for a new air traffic system, and the outage makes that case for the administration better than any speech. The second is private and slower: airlines will report what a day of cancellations cost them, and JPMorgan will have to explain how a bug inside one bank reached others.

The risk the Fed’s contacts rate among the gravest is the one that did not happen this week: an attack timed for when systems are already fragile. This week showed how fragile they are without one.

Disclosure

This is analysis and opinion, not investment advice.

ContactWrite to the Notebook

Something to add?

Spotted an error, or a source this piece should cite? Want your own research linked or featured? Tell us. We read every message.

Keep reading

Archive