US: After Microsoft and Airplanes, a Banking Glitch Disrupts Thousands of Customers

Written by: Adel Khelifi on November 17, 2026

In five days, three major IT outages disrupted essential services in the United States.

Following the difficulties faced by Microsoft 365 and the nationwide grounding of takeoffs ordered by civil aviation authorities, thousands of customers of major American banks reported, on Monday, November 16, 2026, problems accessing their accounts or carrying out transactions. At the origin of the main banking incident was a software bug at JPMorgan Chase.

The sequence of these events raises an important question: how can strategically critical digital infrastructures be disrupted by technical failures?

If their proximity in time is striking, there is no evidence to conclude a coordinated cyberattack or a common cause.

The Essentials

November 12: a global outage affects Outlook, Exchange Online and several Microsoft 365 services.

November 13: the FAA suspends takeoffs in the United States for nearly five hours, following a failure of the air traffic control communications network.

November 16: a software bug at JPMorgan Chase slows banking transactions and indirectly affects some customers of other institutions.

Cyberattack: no verified element links the three incidents to a common malicious operation.

Monday, November 16: customers of large banks face difficulties

On Monday, customers of JPMorgan Chase, Bank of America, Wells Fargo, U.S. Bank and other American institutions reported problems logging in, viewing account details, or processing banking transactions.

Downdetector, which collects user-reported issues, logged several thousand complaints during the day. Some users said they could not access their banking app, while others experienced delays in transactions.

JPMorgan Chase acknowledges a software bug in its internal systems

Asked by Reuters and several American media outlets, JPMorgan Chase explained that a software bug affecting internal computer systems hosted on its own facilities slowed the processing of some transactions.

The bank said that its customers retained access to their accounts and funds, even though some operations required more time than usual. Difficulties accessing online services and certain ATMs were nevertheless reported by users.

JPMorgan noted that it had no evidence of a cyberattack and described the incident as a temporary technical problem.

On Monday evening, around 6:30 p.m. in New York, or 12:30 a.m. Tuesday in Tunisia, Chase announced that transactions were once again being processed normally.

Bank accounts were not frozen

The outage did not correspond to a general blocking of funds nor to a shutdown of the American banking system. The main issue concerned the processing and access to certain operations. The exact number of affected customers and the total financial cost of the incident have not been established.

Why were other banks affected?

One of the most revealing aspects of this incident concerns interbank communications.

When a client of one bank initiates a transfer to or from a JPMorgan Chase account, the operation also depends on Chase’s processing. If that processing slows down, the customer of the other bank may notice a delay, even though their own institution is functioning normally.

This is what U.S. Bank explained, noting that its own systems were not directly affected. Some of its customers could nonetheless experience delays on transactions involving other institutions.

The instant payments platform Zelle also received reports. Its operator, Early Warning Services, nevertheless stated that the Zelle network continued to operate normally.

Thus, the issue for certain transactions lay in the participating banks’ systems rather than in Zelle’s central infrastructure.

Therefore, a localized outage at a large institution can have consequences for customers of other institutions without causing a shutdown of the entire financial system.

Friday, November 13: the United States suspends takeoffs

Three days before the banking incident, the United States experienced a disruption of a different kind.

On Friday November 13, 2026, around 3:30 p.m. Eastern Time, the Federal Aviation Administration (FAA) ordered a nationwide suspension of takeoffs.

This decision was taken as a precaution, following a malfunction of the telecommunications network used for communications and certain radar data flows in air traffic control.

Planes already in flight were able to continue their operations under safety procedures. The FAA announced the stabilization of the systems and the resumption of air movements starting at 20:15, i.e., about four hours and forty-five minutes after the interruption began.

According to the FAA’s tally, about 12,462 flights were canceled on November 13, including 9,082 cancellations by major airlines. The agency explicitly notes that not all of these cancellations are directly attributable to the nationwide takeoff suspension.

The U.S. Department of Transportation says, for its part, that more than 3,500 flights were grounded during the interruption, before a gradual resumption of operations.

A router and an overloaded network at the origin of the aviation crisis

Initial FAA investigations highlighted instability in aging equipment faced with an abnormal surge of data on its telecommunications network.

The agency cites a rate of about 1,000 connection attempts every four to five seconds, which disrupted communications and radar flows.

Two sites were identified in the initial inquiry: a radar installation in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where contractor L3Harris had recently deployed a new router.

The FAA explained that it had isolated the problematic traffic sources and disabled certain features on routers similar to a preventive measure. The technical investigation was to determine precisely the mechanisms of this failure.

This episode shows the consequences that a disruption of the IT network can have in a sector where the availability of communications is a critical safety condition.

Thursday, November 12: Microsoft 365 hit by a global outage

The sequence began on Thursday November 12, with a major outage of the Microsoft 365 ecosystem.

Users reported difficulties accessing Outlook, Exchange Online, Teams and Copilot, as well as certain features of other Microsoft services. Companies relying on these tools faced issues with messaging and delays in email routing.

The services were progressively restored, Microsoft placing the end of the main incident at Friday, November 13 at 11:10 a.m., New York time.

Microsoft’s preliminary analysis, published after the incident and reported on November 16 by BleepingComputer, describes a technical issue more complex than a simple transient overload.

A software defect introduced in a July 2026 update had remained without visible consequences for several months. It is said to have been triggered by a combination of factors, including a traffic shift related to Teams and already reduced capacity on a portion of the servers.

According to this preliminary report, more than 80% of the affected network gateway servers became unavailable during the cascading failure.

The mechanism is fairly straightforward to understand: when a group of servers stops responding, connections are redirected to the remaining servers. If those cannot absorb the extra load, they can be affected in turn, gradually amplifying the outage.

The common thread: dependence on digital infrastructures

The three incidents do not have a demonstrated common cause. However, they each illustrate a form of dependence: on Microsoft’s mail servers, on the FAA’s communications network, and on JPMorgan Chase’s transaction processing systems. In these three sectors, a technical failure can disrupt a large number of users or operations.

Coordinated cyberattack: no evidence at this stage

The succession of outages affecting essential services sparked questions on social networks. Some users mentioned a coordinated cyber operation targeting the United States.

The publicly released technical details do not support this hypothesis.

Microsoft described a chain of software defects and load-management difficulties. The FAA identified a failure in its telecommunications network. JPMorgan Chase acknowledged an internal software bug and said it had found no sign of a cyberattack.

Thus, one must distinguish the chronology of the incidents, which is verified, from the hypothesis of coordination among them, which currently rests on no public evidence.

What are the economic consequences?

The disruptions had tangible effects on users: delayed emails, travel cancellations or postponements, difficulties accessing accounts, and slowed banking transactions.

Their economic consequences can take various forms: costs of reorganizing for businesses, additional expenses for travelers, temporary disruption of certain activities, and mobilization of technical teams to restore systems.

However, no global, audited financial assessment of the three outages has been published. Adding non-comparable estimates to produce a total cost would be misleading.

In banking terms, it is also important to distinguish a payment delay from a definitive financial loss. The incidents reported on Monday mainly concerned access to services and processing times, not the disappearance of deposits.

And in Tunisia, are we safe from this type of outage?

These American events invite reflection on the resilience of digital infrastructures in other countries, including Tunisia.

Banks, telecom operators, administrations, and Tunisian businesses also depend on information systems, communications networks, and technical service providers. A service interruption can have operational consequences when contingency measures are insufficient.

The general lessons concern in particular testing of updates, the ability to switch to backup systems, business continuity procedures, and coordination among interdependent operators.

Three distinct outages, one common question about resilience

At the end of these five days of disruptions, the Microsoft services involved were restored, takeoffs resumed in the United States, and JPMorgan Chase announced a return to normal processing of its transactions.

The sequence of incidents does not prove the existence of a coordinated attack. It does, however, highlight a common issue: the ability of large infrastructures to stay operational when software, a network device, or a central processing system experiences a failure.

In an economy where exchanges, transportation, and communications rely heavily on computing, the continuity of essential services depends as much on the reliability of systems as on their ability to withstand a failure and recover quickly.

Adel Khelifi

Adel Khelifi

My name is Adel Khelifi, and I’m a journalist based in Tunis with a passion for telling local stories to a global audience. I cover current affairs, culture, and social issues with a focus on clarity and context. I believe journalism should connect people, not just inform them.