On Monday, 16 November, many people in the United States found that something was wrong with their banking. Customers had trouble reaching their accounts and completing payments. Some Chase customers saw a message saying that some services were not available and they should try again later.
The trouble began at JPMorgan Chase, the largest bank in the country by total assets. The bank said a software bug in one of its own hardware systems, kept on its premises, was slowing down transactions. It also said clearly that this was not a cyberattack. Thousands of customers reported problems. According to outage-tracking site Downdetector, the reports peaked around 2 pm US Eastern time and then slowly came down.
Here is the interesting part. The problem was not limited to Chase customers. People who bank with Bank of America, Wells Fargo and some other banks also reported trouble. Yet some of those banks, such as US Bank, said their own systems were not directly affected. So how did the problem spread?
The answer is that banks do not work alone. When money moves from one bank to another, both banks have to talk to each other and agree on the transaction. If one side is slow, the payment is slow for both. Think of a busy road with one bridge. Even if every other road is clear, any traffic that needs to cross that bridge gets stuck. A Chase spokesperson explained it in similar terms. Other banks felt the slowness only when a transaction involved Chase, and he said it was not a systemic issue.
This is also why Zelle was in the news. Zelle is the money transfer service that many US banks offer so that people can send money to friends and family almost instantly. It is run by a company called Early Warning Services, based in Arizona, which is owned by several big banks. These include Bank of America, Capital One, JPMorgan Chase, PNC Bank, Truist, US Bank and Wells Fargo.
On Monday, Zelle said its own network was running normally. That may sound confusing, because some people did have trouble with Zelle payments. But most people use Zelle through their own bank or credit union. So if a payment involved a Chase account, it could be delayed even though Zelle itself had no fault. US Bank gave a similar warning, saying its systems were not directly hit but Zelle payments involving other institutions could take longer.
What about people’s money? Chase said its customers still had access to their accounts and funds. Some customers, however, said they were unable to get in. Both things were reported, and that is worth remembering when you read about an outage like this. Experiences were different for different people.
By about 6:30 pm Eastern time on Monday, Chase said its transactions were posting normally again. But “back to normal” does not always mean every delayed payment was completed at that same moment. A simple habit helps here. Before you send a payment a second time, check your account first, so you do not end up paying twice.
The timing made people nervous, and that is understandable. Just days earlier, on Thursday, 12 November, Microsoft had a major outage that affected services such as Outlook, Teams and its Copilot assistant. The next day, on Friday, 13 November, the US Federal Aviation Administration stopped flights across the country after a technical failure affecting air traffic control. With three big disruptions within five days, it was natural to ask if they were linked.
So far, no connection has been confirmed. Officials and company leaders have said the incidents were unrelated and had different causes. Microsoft said there was no indication that its outage came from a cyberattack or other malicious activity. The aviation disruption involved faulty equipment. And Chase said its own problem was simply a software bug.
Not everyone is fully satisfied with that. Jody Westby, who heads a cybersecurity advisory firm called Global Cyber Risk, told Al Jazeera that she was worried people were quickly accepting “technical issue” as the whole story. She said the public deserves a more complete explanation and that these incidents need proper investigation. That is one expert’s view, but it shows that questions remain. Reports so far also do not say exactly which hardware system failed at Chase.
The bigger lesson from Monday is simple. Modern banking is a web of connections. Your bank may be perfectly healthy, but if a major partner in that web slows down, you can feel it too. One bug in one system was enough to send ripples across several banks and a payment service in a single day.
Subscribe Deshwale on YouTube


