When a Transfer is Delayed: What Happened at Which Bank - Weaknesses of a Digital Society Seen in U.S. Disruptions

When a Transfer is Delayed: What Happened at Which Bank - Weaknesses of a Digital Society Seen in U.S. Disruptions

The Day After the Email, It Was the Airplane, and at the Start of the Week, the Bank: Commonalities in the IT Disruptions in the U.S.

At the San Francisco airport, passengers had already been waiting on the plane for about an hour. Then, the captain announced that all flights were halted due to a network issue. Even after 30 more minutes, the aircraft remained stationary. A passenger wrote on the U.S. forum Reddit, expressing concern that they might not make their connecting flight.

Another user replied to that post, noting that since flights were halted nationwide, the connecting flight likely hadn't taken off yet either. While it might sound like a consolation, it highlights the complexity of large-scale disruptions. Even if you know how many minutes your flight is delayed, it doesn't necessarily mean you can rearrange your subsequent plans.


Four Different Troubles Occurring Over Four Days

On November 12, 2026, Microsoft's email service "Outlook" experienced widespread disruptions. The company cited network load as the reason. The following day, on the 13th, the U.S. Federal Aviation Administration (FAA) instructed all departing flights nationwide to temporarily hold. The issue here was a control communication malfunction related to routers, devices that route communication paths. For safety, flights about to take off were kept grounded.

On the 16th, at the start of the week, users of several major U.S. banks reported issues with online transactions. What’s important here is that the banks where users noticed anomalies and the banks where processing was delayed were not necessarily the same. JP Morgan Chase explained that a software malfunction running on its equipment delayed transaction processing, potentially affecting other banks receiving those transactions. Even if multiple bank names appear in disruption reports, it doesn't necessarily mean all their systems failed simultaneously.

On the same day, some United Airlines departure flights also experienced delays. According to the pilots' union, they were unable to deliver the final weight data of the aircraft to the departing flights. This issue was different from the FAA's communication problem that halted nationwide departures three days earlier. The company explained that flights already in the air were not affected and announced recovery within the same day.


For a Plane to Fly, It Needs "Numbers" Besides the Aircraft

The United Airlines case illustrates well how computer malfunctions can halt real-world movement. Even if passengers are seated and see the runway outside the window, takeoff requires data based on the flight's weight and balance. If the necessary numbers don't reach the cockpit, preparations for departure stop there. The hold itself is a decision made to ensure safety.

A similar situation occurs in banking. For example, if someone is waiting for a deposit from a client, repeatedly reopening their bank app won't change the display if processing is delayed on the sender's side. What users see is just the balance number, but for that number to change, tasks must be completed by another organization.

In an interview with Canada's Global News, Professor Ali Butt from Virginia Tech explained that in complex systems, the failure of a single component or the impact of routine updates can rapidly spread. A bug that had been lurking might surface for the first time under certain conditions. No evidence has been presented to link the events over several days to a single cause. However, each event shows a structure where "the next task is waiting for information from the previous task."


What Passengers Confirmed on Social Media Was the Extent of the Disruption

On the 13th, a Reddit user at the New Orleans airport posted that they were told by the captain they couldn't take off due to an air traffic control issue and were waiting for additional information. Short replies came in, stating that the same situation was occurring in Minneapolis and Denver. The situation at other airports, invisible from inside the plane, was gradually being communicated.

 

In the same thread, there were voices questioning the events following the Microsoft disruption the previous day. By connecting posts from passengers across various locations, it became clear that the hold wasn't just about their own flight. However, the causal relationship with the previous day's email disruption remained unknown. At the time of Global News' interview, no company had attributed the series of troubles to a cyberattack, nor had there been any explanation that AI was the cause.

For passengers in San Francisco, knowing it was a nationwide issue was meaningful because it provided clues about the status of their connecting flights. Even just communicating the extent of the disruption can help people use that information to adjust their own plans.


"The Next Report" That Should Reach Japanese Users

Evan Wright, who researches information policy at the University of Toronto, points out that services like email have become concentrated among a few large companies. Normally, many people can conveniently use the same system. But on the day that system stops, many will simultaneously seek alternative means.

If placed in the same situation in Japan, what kind of information would be helpful? At an airport, distinguishing that "the issue affects pre-departure flights and not those already in the air" is meaningful even for families waiting for arrivals. In banking, knowing that "the transaction has been accepted, but reflecting it in the recipient's account is taking time" can help avoid the dilemma of whether to resend the money.

Identifying the cause can take time. Even so, once it's understood, information about how far the impact extends, whether completed procedures are valid, and when the next update will be released can be communicated. For someone watching the clock on the plane, the immediate decision is not about what happened to the router, but whether to contact their next destination immediately.


Sources