A Nov. 16 Chase software bug disrupted banks and Zelle, and the FDIC listed 6 failures in 2026. Here is what each meant for customers' money.

When people say their bank is down, they can mean two very different things, and in 2026 Americans saw both. With the loud kind, customers could not reach their money, but none of it was lost. Customers trying to sign in during the November disruption met login errors. Chase mentioned those customers still had access to their accounts and their money, according to TIME. The fear of loss and the reality did not match. The quiet kind is a bank closing for good. Such closures were rare going into this year, with just two bank failures in the U.S. in all of 2025, according to the Chicago Sun-Times. Closures picked up in 2026 but stayed uncommon. How much noise a banking problem makes and how much harm it does are two separate questions, and the answers often differ.

According to recent reports, the November disruption felt bigger than it was partly because of when it came. It followed a Microsoft $MSFT outage on the Thursday before and an air traffic control outage on the Friday, then bank customers ran into trouble on Monday, according to The Associated Press. Nothing ties those three breakdowns to a common cause. What they share is timing. Still, a frozen login screen at the end of a week like that feels like a system in danger, while a small bank quietly changing hands on a Friday feels like nothing at all. People's instincts about which trouble is serious can easily run backward, and sorting the two kinds apart is the useful work.

USA TODAY set out to explain the Nov. 16 bank disruption that began at JPMorgan $JPM Chase and to list the year's bank failures, with entries ranging from Zelle to Nano Banc and Tioga-Franklin Savings Bank. The FDIC listed six bank failures in 2026, and none of them had any link to the November disruption. Each was a bank closed over its finances, not a technology breakdown. Read together, the two kinds of trouble show where the real cost of a banking problem falls. Sometimes it is a customer's lost afternoon. Sometimes it is a charge to the insurance fund that backs deposits. The question for any bank customer is which kind of trouble ever reaches their money, and why.

The November 16 bank disruption had a single source, JPMorgan $JPM Chase, and not a breakdown across the whole banking industry. The cause sat inside one institution's own systems, yet customers felt it at once and in large numbers. At the peak, nearly 4,800 to 5,000 reports of problems with Chase reached Downdetector, according to USA TODAY. That many people speaking up in the same stretch of time makes an outage feel like an assault, and the natural first guess is a hack.

In a recent development, the outage had no attacker behind it, which places it among the ordinary failures that have disrupted large banks before. Chase and DHS officials found no evidence of a cyberattack. Major banks have lost their systems to mundane faults in the past. At one large bank, smoke set off an automatic shutoff that cut power to a data center, and in 2016 Bank of New York could not send or receive SWIFT payment messages for 19 hours, according to a Federal Reserve analysis published in 2022. A fault with no villain behind it can still drag on for hours. Ruling out an attacker removes the villain from the story, but it does not remove the risk. A bank's own systems can fail for long stretches without anyone breaking in.

Sources indicate that the fault began at one bank. Whether it stayed there is the next question.

In a recent development, on Nov. 16, customers of JPMorgan $JPM Chase were not the only ones who complained. TIME reports that people also flagged problems with Bank of America $BAC, Wells Fargo $WFC, Capital One $COF, Truist and Zelle that day. Bank of America, the next most reported, drew just over 2,000 reports on Downdetector, and Wells Fargo, Capital One, Truist and Zelle drew hundreds each. Those totals were far lighter than the flood of complaints at Chase, where the trouble began. A pattern that heavy at one bank and much lighter at the rest most likely reflects trouble spilling over from Chase, not six separate breakdowns at the same moment.

A bank can draw a flood of complaints while nothing inside it has broken. U.S. Bank customers filed 1,060 reports, according to TIME, yet the bank denied any fault of its own. "U.S. Bank systems are not directly impacted," a U.S. Bank spokesperson remarked. The likeliest explanation is that its customers were trying to send money to or through Chase that day. A reader who sees their own bank named in an outage report should expect that a payment might stall, not that the bank itself is in trouble.

Zelle was the most misunderstood name among the services customers reported. TIME reports that Zelle, according to its spokesperson, keeps no separate accounts for consumers and holds none of their money. A stalled Zelle payment is a stalled message between two banks, and the dollars stay at the bank on one end or the other. Zelle links many banks, so customers whose own banks were working could still find their transfers held up when Chase had trouble. When Zelle seems down, the banks on either end are the place to look. A delayed transfer could still leave someone waiting for money they needed that day, but the money itself stayed at a bank the whole time.

Customers made the November 16 disruption public through a flood of complaints. At the peak, nearly 4,800 to 5,000 people reported problems with Chase, according to Downdetector. That crowd was large enough to make the day feel like a national emergency, but it counts people who spoke up, not people who lost money. Reports about Zelle came in as well, though many people think of the payment app as separate from any one bank. Early Warning Services owns Zelle, The Associated Press reports, and that company's owners include financial institutions. Banks share that network, so customers who never opened Chase's app could still feel one bank's trouble. The people caught up in the outage were not only Chase customers. Anyone whose payment touched Chase that day could be caught up in it.

In a recent development, the disruption followed individual payments, not whole banks, and customers elsewhere slowed down only when Chase stood on the other side of a transfer. "This is not a systemic glitch — other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us," Joe Evangelisti, spokesman for JPMorgan $JPM Chase, told The Associated Press. That is the bank's own account of its own failure, and readers should weigh it as a claim, not a settled finding. It does fit the complaints about Zelle, whose job is moving money from one bank to another. For someone who banks elsewhere, the risk that day came from sending money to or through Chase, not from any fault at their own bank.

The complaints filled every board that Monday, yet people felt the outage only when their payments crossed the connections between banks, and those connections are the weak point worth watching.

Sources indicate that JPMorgan $JPM Chase had its own systems working again on the same day the trouble began. Users had started flagging errors by 11:30 a.m. ET, according to CNBC. While complaints were still arriving, the bank promised a fix before the day was out. "We're working diligently to resolve this by the end of the day today," a JPMorgan spokesperson noted. USA TODAY reports that Chase said its transactions were processing normally on Nov. 16, so by the bank's own account it kept that promise. Both the promise and the all-clear came from Chase, and the all-clear covered only its own transactions.

Customers dealt with the trouble for longer than the bank's timeline suggests. People kept reporting problems through Monday night, and the reports largely subsided only in the early hours of Tuesday, Nov. 17. No one has given a separate time when service returned to normal at other banks or at Zelle. For anyone outside Chase, the clearest sign that the trouble had ended was the drop in complaints overnight.

The outage gave no sign of a threat to the money in customers' accounts. Chase and officials at the Department of Homeland Security found no evidence of a cyberattack. By Chase's account, ending the outage meant fixing a fault inside its own systems, not driving out an intruder. For customers, the documented cost was the wait for logins and payments to work again.

A larger question remains: whether the banking system is built to absorb this kind of failure.

In a recent development, the bank where a disruption starts claims little about whose payments end up stuck, because banks rely on the same few service providers and send payments to one another all day. The November 16 disruption began at JPMorgan $JPM Chase, according to USA TODAY, but the customers held up that day banked across the system. Federal Reserve Board analysts Chase Englund and Zach Modig report that in a scenario where one provider in their study, which they call Provider 2, was disrupted for an hour on a sample day, only one of the 23 firms most central to the payment network bought its service directly. Nearly all of the banks at the center of that scenario had no direct tie to the provider in trouble. A customer whose bank has no tie to Chase can still get caught in a Chase outage, and the more useful question is whether that bank sends payments along the same paths.

Community banks appear among the firms the payment network leans on most. In the hour the analysts studied, eight of those central firms belonged to a group of community bank holding companies, according to analysts at the Federal Reserve Board. Choosing a smaller bank does not, on its own, keep a customer away from the part of the network where trouble can spread.

For a household or a business, the real test of an outage is whether the rent, the payroll or the transfer due that day went through, not how long the login screen stayed frozen.

Sources indicate that the year's string of bank closings began at a modest lender in Chicago. Metropolitan Capital Bank & Trust closed on Jan. 30, the first of the six bank failures the FDIC recorded in 2026, according to USA TODAY. The Chicago Sun-Times reports that the Illinois Department of Financial and Professional Regulation shut down the bank, which was based in the city's River North neighborhood. A state regulator closed it over its finances, and none of its systems had broken. It was also too small to signal trouble in banking as a whole, with about $261.1 million in assets as of Sept. 30, a modest sum by banking standards. Its customers kept their money because First Independence Bank of Detroit took over all of the deposits, and their accounts continued at the fresh bank.

The failure did cost money, but the bank's depositors did not pay it. Acting as receiver, the FDIC put the price of this closing for its Deposit Insurance Fund at about $19.7 million, according to the Chicago Sun-Times. The FDIC keeps that fund to cover losses of this kind. "We want to be clear that no depositor will lose any money as a result of this action," noted Susana Soriano, acting director of the Division of Banking at the Illinois Department of Financial and Professional Regulation. A bank failure can carry a real price and still leave every customer's account whole, because the FDIC pays that price from its insurance fund.

Sources indicate that A failed bank is not latest to Chicago. The city has had 22 bank failures since 2000, according to the Chicago Sun-Times, and this closing adds one more to that long record. Soriano notes the state closed this bank because it was operating in an unsafe way and did not have enough capital. That broad finding is the only reason on record, and no specific cause has been made public, so the failure points to no particular danger for other banks.

Nobody has explained in public what went wrong inside the bank, but its customers' deposits were already safe at a fresh bank.

Community Bank and Trust - West Georgia closed so smoothly that its customers lost little more than a weekend. The bank became the second failure of 2026 on May 1, months after the year's first in January, according to the FDIC. That gap shows how rarely banks closed this year. The Georgia Department of Banking and Finance shut the LaGrange, Ga., community bank, and Anchor Bank of Palm Beach Gardens, Fla., took over its insured deposits. Customers ended up with a new bank rather than none, and the old branches reopened as Anchor Bank the following Monday, May 4. They saw none of the error screens that marked the November lockout.

According to recent reports, the quiet weekend hid an expensive failure. Community Bank and Trust was a small lender that held $288 million in assets at the end of 2025, according to the FDIC. The modest size of the bank helps explain why its closing drew so little notice. Yet covering the failure is expected to take approximately $97 million out of the Deposit Insurance Fund, a sum that is large next to the bank's own size. Readers can't judge the price of a bank failure from the size of the bank alone. Regulators can close a small bank with little public notice and still draw heavily on the fund that stands behind every insured account.

The only depositors who faced real risk were those with balances above the insurance limit. Approximately $27 million in deposits went beyond that limit, a figure likely to change, according to the FDIC. That money sat in the bank's largest accounts, and it was the only depositor money without insurance behind it. The pattern here runs opposite to the November disruption. In November, nearly everyone was inconvenienced and no one's money was at stake. In LaGrange, almost no one was inconvenienced, and the only money without a guarantee was the part of the largest balances that went past the insurance limit.

A bank on the federal failure list can be one that few people outside a single small town have ever heard of. Kentland Federal Savings and Loan Association, a savings and loan in Kentland, Ind., failed on July 10, 2026, according to an FDIC list of the year's bank failures reported by USA TODAY. It was a very small bank, with about $3.65 million in deposits as of March 31, according to Financial Regulation News. A count of failures treats a bank of that size the same as a much larger one, and the number of closings alone says little about how much money was at stake.

Kentland did not close because of a hack or a system crash. Its own finances gave out. Financial Regulation News reports that the Office of the Comptroller of the Currency shut the association after finding it critically undercapitalized. In plain terms, the bank no longer had enough capital of its own to stay open. Customers cannot check a bank's capital on an app, and trouble of this kind never demonstrates up as a frozen login screen. The problem that ends a bank can be the one its customers are least likely to see coming.

Industry observers note that kentland's depositors did not lose their money. Their deposits are now held at Kentland Bank and remain FDIC-insured, according to Financial Regulation News. Kentland Bank is a separate institution with no affiliation to the failed association. Customers' accounts changed hands, even though the name on their statements barely changed. The town's loss is practical rather than financial, because the association's only branch is closing for good. The FDIC expects to pay for the failure from its Deposit Insurance Fund, not from account holders, at an estimated cost of about $1.2 million, according to an FDIC estimate reported by Financial Regulation News.

A failure this quiet still costs real money, and Kentland's depositors were not the ones who paid it.

In a recent development, bank failures came closer together in midsummer 2026. Small Business Bank, a lender in Lenexa, Kan., shut on July 17 and became the year's fourth failure only seven days after the Kentland savings and loan closed, according to USA TODAY. The Kansas Office of the State Bank Commissioner closed the bank, and the FDIC took charge as receiver, according to the FDIC. Whether a bank's collapse ever reaches its customers' money depends on that handoff to a federal insurer more than on the failure itself.

For depositors, the failure changed little beyond the name on the sign. Customers got no warning, and the FDIC reports that the public receives no advance notice when a bank is closed. The Farmers State Bank of Oakley, Kan., took on substantially all of the deposits along with certain assets, so savers' money moved to the fresh bank together with their accounts. The old locations reopened as Farmers State Bank branches, and customers walked through the same doors under a new name. The November outage kept people away from money that was never at risk. This failure ended a bank, and its customers went on banking.

In a recent development, customers who already held accounts at Farmers State Bank have one detail to know. Their transferred deposits and their existing accounts at the bank are insured separately, according to the FDIC, so the two sets of balances do not fall under a single coverage limit. The rescue covered the depositors and stopped short of the bank's owner. Gardner Bancshares, Inc., the holding company that owned all of the bank's shares, was not included in the receivership.

The safety net carried the depositors through the failure and left the owner outside it.

Industry observers note that state regulators kept closing banks through the summer, and Tioga-Franklin Savings Bank in Philadelphia became the fifth of the year's six FDIC-listed failures, according to USA TODAY. The FDIC reports that Pennsylvania's Department of Banking and Securities closed the bank on Friday, Aug. 21, 2026. The federal agency counts the closure among the year's failures, but a state agency made the decision. The FDIC stepped in only after the state acted, serving as receiver to take over and wind down what was left of the bank. Anyone tracking the national tally of bank failures is therefore, at least in this case, tracking a state regulator's decision about one local bank.

Industry observers note that depositors at Tioga-Franklin kept the basic services they depended on, even though the closure came without any advance public notice, according to the FDIC. The public learned of the failure only after the bank had already shut. Direct deposits continued as usual through the change of ownership, so paychecks and benefits kept arriving on schedule. The physical bank stayed in place too. Customers can keep using the same locations, which now operate under the name of Second Federal Savings and Loan Association of Philadelphia, a bank based in the same city. They could walk into the same buildings and deal with a local institution rather than a distant one.

A bank closed in Philadelphia that summer, yet its depositors kept both their direct deposits and their branches.

Nano Banc, a lender in Irvine, Calif., failed on Sept. 25, the latest of the six bank failures in 2026, according to FDIC figures reported by USA TODAY. It was a state-chartered member of the Federal Reserve, so the Fed oversaw it directly, according to the Federal Reserve. Regulators had been watching the bank for years before it closed. As early as February 2021, the bank had agreed in writing to corrective terms set by the Federal Reserve Bank of San Francisco. Nano Banc did not break overnight. Its trouble had been on the public record long before September.

The warnings grew more serious as regulators moved from a written agreement to legal orders. The state of California ordered the bank to cease and desist in December 2021, and the Fed followed the next month with a consent order that became binding on Jan. 18, 2022, according to the Federal Reserve. By the time of the 2022 order, examiners had found unsecured loans to shareholders of Nano Financial Holdings, the bank's parent manufacturer. When a bank lends to its owners without collateral, it puts their interests ahead of the safety of depositors' money. Nano Banc also had no permanent chief executive or chief financial officer in 2022, while it still had to carry out the corrective steps its 2021 agreement with the Fed required. The bank faced a large repair job with no one permanently in charge. That was a plausible warning sign, though not a forecast of failure.

The 2022 order reached past the bank to the companies that controlled it, binding both of its holding companies, Allegiant United Holdings and Nano Financial Holdings, according to the Federal Reserve. That fits a problem that involved the bank's owners. Still, a record of warnings does not establish a cause, and no reason for the September closing has been made public. The orders from 2021 and 2022 are evidence of long-running trouble, not an explanation of why the bank failed.

It has been revealed that the warnings that mattered here never appeared as error screens. They were public orders from regulators, issued years before the failure, and for anyone worried about their own bank, those orders are a quieter and more telling place to look.

→ Read original article