Field report NE-46 / J5 · sheet /macro

Boardroom MacroFiled from the territory

Chase's November Outage Freezed Logins; Six 2026 Bank Failures Hit Insurance Fund, Not Depositors

Chase's Nov. 16 outage froze logins for thousands but touched no balances, while six 2026 bank failures cost the FDIC's insurance fund heavily and risked only uninsured deposits above the limit.

Grid
NE-46 / J5
Surveyed
November 20, 2026
Reading
5 min read
Correspondent
Priya Raman
1 Chase outage and 6 bank failures in 2026 reached customers' money differently
Fig. NE-46 / J51 Chase outage and 6 bank failures in 2026 reached customers' money differently — don2365 / pixabay

Field notes

  1. Nearly 4,800–5,000 Downdetector reports peaked during Chase's Nov. 16, 2026 outage; Chase and DHS found no evidence of a cyberattack.
  2. The FDIC recorded six bank failures in 2026, up from two in 2025, and none were linked to the November disruption.
  3. Community Bank and Trust – West Georgia's failure is expected to cost the Deposit Insurance Fund about $97 million against $288 million in assets.
  4. About $27 million in deposits exceeded the insurance limit at Community Bank and Trust — the only depositor money without a guarantee.
  5. Roughly 26% of daily Fedwire volume moves after 5 p.m., so evening outages can push payments to the next settlement day.

Nearly 5,000 customers reported problems with JPMorgan Chase on Nov. 16, 2026, yet not a dollar of their money was at risk — while the year's six bank failures, which drew far less noise, cost the FDIC's insurance fund tens of millions and put only uninsured balances in danger. That contrast is the story of American banking trouble in 2026, and it runs opposite to instinct.

The loud kind of trouble and the quiet kind rarely overlap. The November disruption locked customers out with login errors but left accounts untouched, according to TIME. The quiet kind — a regulator closing a bank over its finances — ended six institutions this year, and none of those closures had any link to the November outage, according to the FDIC list reported by USA TODAY.

What actually failed on Nov. 16?

A single institution: JPMorgan Chase. At the peak, roughly 4,800 to 5,000 problem reports reached Downdetector, according to USA TODAY. Chase and Department of Homeland Security officials found no evidence of a cyberattack. The cause sat inside one bank's own systems, and Chase had them working again the same day, by its own account.

Mundane faults have hit large banks before. In 2016, Bank of New York could not send or receive SWIFT payment messages (the international bank-to-bank messaging network) for 19 hours, according to a Federal Reserve analysis published in 2022.

The disruption felt bigger because of timing. It followed a Microsoft outage on the Thursday before and an air traffic control outage on the Friday, then hit bank customers on Monday, according to The Associated Press. Nothing ties the three breakdowns to a common cause. They share only a calendar.

How far did the trouble spread?

Customers also flagged problems with Bank of America, Wells Fargo, Capital One, Truist and Zelle that day, TIME reports. Bank of America drew just over 2,000 Downdetector reports; the others drew hundreds each — far lighter than Chase's flood, which suggests spillover rather than six simultaneous breakdowns.

U.S. Bank customers filed 1,060 reports even though the bank denied any fault. "U.S. Bank systems are not directly impacted," a U.S. Bank spokesperson said. The likeliest explanation: those customers were sending money to or through Chase.

Zelle, the payment network owned by Early Warning Services — itself owned by financial institutions, per the AP — drew the most confusion. Zelle keeps no separate consumer accounts and holds none of their money, its spokesperson said. A stalled Zelle payment is a stalled message between two banks; the dollars stay at a bank on one end or the other.

Joe Evangelisti, a JPMorgan spokesman, said: "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." That is the bank's own account of its own failure. It fits the complaint pattern, but readers should weigh it as a claim.

Users flagged errors by 11:30 a.m. ET, CNBC reports, and a JPMorgan spokesperson promised: "We're working diligently to resolve this by the end of the day today." Chase said transactions were processing normally on Nov. 16. Customers kept reporting problems into Monday night, and reports largely subsided only in the early hours of Tuesday, Nov. 17.

What did the six bank failures cost?

Each closure was a bank shut over its finances, not a technology breakdown:

  • Metropolitan Capital Bank & Trust, Chicago, closed Jan. 30 by the Illinois Department of Financial and Professional Regulation. About $261.1 million in assets; roughly $19.7 million cost to the Deposit Insurance Fund. First Independence Bank of Detroit took all deposits. "We want to be clear that no depositor will lose any money as a result of this action," said Susana Soriano, acting director of the state's Division of Banking. Chicago has had 22 bank failures since 2000.
  • Community Bank and Trust – West Georgia, LaGrange, closed May 1. $288 million in assets; expected cost near $97 million to the fund. Anchor Bank of Palm Beach Gardens took insured deposits; branches reopened May 4.
  • Kentland Federal Savings and Loan, Kentland, Ind., closed July 10 after the Office of the Comptroller of the Currency found it critically undercapitalized (too little of its own capital to stay open). About $3.65 million in deposits; estimated $1.2 million cost. Deposits moved to Kentland Bank, a separate institution.
  • Small Business Bank, Lenexa, Kan., closed July 17 — seven days after Kentland. Farmers State Bank of Oakley took substantially all deposits.
  • Tioga-Franklin Savings Bank, Philadelphia, closed Aug. 21 by Pennsylvania's Department of Banking and Securities. Branches now operate as Second Federal Savings and Loan Association; direct deposits continued as usual.
  • Nano Banc, Irvine, Calif., closed Sept. 25. The Fed had issued corrective orders since February 2021, including a binding consent order of Jan. 18, 2022, after examiners found unsecured loans to shareholders of parent Nano Financial Holdings. No reason for the closing has been made public.

The FDIC gives the public no advance notice when it closes a bank. Customers simply walk through the same doors under a new name.

Whose money was actually at risk?

Only depositors above the insurance limit. About $27 million in deposits went beyond it at Community Bank and Trust, according to the FDIC — the largest accounts, and the only money without a guarantee. The pattern inverts November: nearly everyone was inconvenienced then, and no one's money was at stake; in LaGrange, almost no one was inconvenienced, and only the largest balances carried risk.

One structural point matters for anyone banking elsewhere. Federal Reserve Board analysts Chase Englund and Zach Modig found that when one payment provider in their study was disrupted for an hour, nearly all of the 23 most central banks in the network had no direct tie to it. Eight of those central firms were community bank holding companies. About 26% of each day's Fedwire volume moves after 5 p.m., and payments that miss the 7 p.m. Eastern settlement close wait for the next day — even after logins work again.

The real test of a bank problem is whether the rent, the payroll or the transfer went through. Everything else is noise.

via qz.com (Source)

Share this article:

More from Priya Raman

Priya Raman

Show full bio

Senior reporter covering technology and product news in corporate strategy and chief-executive leadership at CEO Frontier.

496 articles

Filed under

Adjacent sheets

« Previous articleNext article »

End of sheetNE-46 / J5 · November 20, 2026