On Monday, November 16, 2026, customers of America's biggest banks found they could not get into their accounts. Online banking stalled, balances would not load, and transfers hung. By the afternoon, outage reports had spiked at Chase, Bank of America, Wells Fargo, U.S. Bank, Capital One and the Zelle payment network — and social media was asking the obvious question: was this a cyberattack? The answer, according to the banks themselves, is no. What happened instead was a software bug inside Chase — and a reminder of how tightly the American banking system is wired together.
The timeline: how the outage unfolded
The first reports appeared on Downdetector, the site that tracks service problems from user reports, at 9:53 a.m. Eastern Time, when Chase customers began flagging trouble with online banking. Plaid — the service many finance apps use to connect to bank accounts — opened an incident for Chase at 10:11 a.m. Bank of America reports began climbing about two hours later, at 11:42 a.m., and Wells Fargo's at 12:46 p.m.
The numbers tell the story of the afternoon. According to USA Today, Chase reports on Downdetector peaked at close to 5,000 soon after 2 p.m. Eastern, and had fallen to about 1,450 by 6:05 p.m. Bank of America eased from roughly 2,100 reports to about 650 over the same period, and Wells Fargo from about 1,050 to roughly 370. By shortly after 7 p.m., JPMorgan Chase told USA Today in an email that transactions "are being processed normally now".
What Chase says went wrong — and what it was not
JPMorgan Chase confirmed to USA Today that the problems stemmed from Chase itself. In its statement, the bank said it "experienced a temporary issue related to a software bug in on-premise hardware systems — it is not cyber related", adding: "This is not a systemic issue — other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us." A Chase spokesperson told the Associated Press much the same thing: "Due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds."
That last point matters. Customers were locked out of apps and unable to see balances, but the bank says money itself was never at risk and accounts remained accessible in principle — the failure was in processing speed, not in the ledger. Chase's support account on X had earlier told a customer it was "currently working to resolve an issue with online banking" and asked users to try again later. The bank said it was working to fix the problem by the end of the day.
The other banks' positions were narrower than the headlines suggested. Bank of America and U.S. Bank each told USA Today that their own systems were not directly hit, and that clients were delayed only when a transaction involved Chase. Wells Fargo acknowledged technical issues on its website but gave no detail about a cause, and has not said whether its problems were connected to Chase. As the Associated Press reported, there is currently no evidence establishing that the outages at the different banks share a single cause — and no evidence of a cyberattack at any of them.
The numbers behind the panic
Downdetector counts are user reports, not a measure of how many people were actually affected, and they can move fast as more people open their apps to check. Even so, the scale is striking: more than 3,300 Chase complaints were logged in one count on Monday afternoon, with around 1,400 combined for Bank of America and Wells Fargo, and thousands more across U.S. Bank, Capital One and Zelle. Customers described being unable to view balances or recent transactions, and being blocked from wire and transfer screens.
The episode lands in an uncomfortable week for American infrastructure. A global Microsoft 365 outage hit on November 12, and the Federal Aviation Administration ordered a nationwide ground stop on November 13 after a technical problem — an event we explained in our report on the FAA ground stop. Some coverage has linked the three events into a pattern. The explanations given so far point to separate technical faults rather than a common cause, and nothing published so far connects them — but the clustering is exactly why the question keeps being asked, and why each new outage now feels bigger than its own facts.
What to do if it happens to you
The practical lessons are simple, and they are worth keeping for the next outage, because there will be one. First, check the bank's own status channel before assuming the worst — Chase's statement arrived on X and in the press within hours, and it ruled out a cyberattack early. Second, remember that Downdetector spikes measure reports, not necessarily a total failure; many customers were unaffected even at the peak. Third, keep a second way to pay: a card from a different bank, or cash, breaks the single point of failure that a one-bank outage creates. And fourth, beware of the scams that follow every bank outage — fake "security check" messages and phishing links spike within hours of the real event.
The November 16 outage was, in the end, a mundane failure with an outsized echo: one bug in one bank's hardware, amplified by the fact that so many payments pass through Chase that a slowdown there looks like a slowdown everywhere. That is both reassuring and worrying. Reassuring, because there was no attack and no money was lost. Worrying, because it took only a software bug — not a hacker, not a storm — to make millions of Americans wonder whether their money was still there. In a week when a Microsoft outage and an FAA ground stop did the same thing to email and air travel, the question is no longer whether big systems fail. It is how many of them can fail at once before the failures start to look like a pattern.
