Emerald Pages
◆
How Chase Caused the Banking “Outage” but Left Black-Owned Banks Unaffected
One software bug at America's largest bank jammed the payment rails for millions and made it look like the whole system was down. Here's how the outage spread — and why it never crossed into Black-owned banks.
Photo: Getty Images
On Monday, November 16, 2026, a routine software update rolled out to JPMorgan Chase's own internal servers — the physical machines inside Chase's data centers, not a cloud provider's. The update contained a defect. By midday, nearly 5,000 customers had filed problem reports, and the ripple was being felt at Bank of America, Wells Fargo, U.S. Bank, Capital One, and Truist. By Monday evening, Chase had fixed the bug and confirmed that online banking and transaction processing had returned to normal. But for a few hours, one bank's problem looked like everyone's problem.
The key to understanding what happened is this: the other banks never actually went down. Their servers, apps, and websites kept running normally all day. What failed was the handshake — the instant, two-way confirmation that has to happen when money moves from one institution to another.
When a customer at another bank tried to send money to or pull funds from a Chase account, their bank's system had to wait for Chase's servers to verify and clear the transaction. Because Chase's servers were bogged down, those external requests timed out or hung in a pending state. The other bank's app, waiting for an answer that never came, displayed a generic "service unavailable" or "transfer failed" message. To the customer staring at their phone, it looked like their own bank had crashed.
Zelle made the illusion worse. Zelle operates as a messaging network between more than 2,500 banks rather than holding funds in a separate account. For a transfer to succeed, both the sender's bank and the recipient's bank must instantly approve the message. Whenever a Zelle payment involved a Chase customer on either end, the message stalled at Chase's servers — triggering error messages for users at completely unaffected banks. Zelle's operator confirmed its platform remained fully functional throughout the day.
What Exactly Went Wrong
According to an FBI official cited in reporting on the incident, Chase rolled out a routine software update earlier that Monday morning. That update contained a bug that clashed with Chase's on-premise hardware systems. Instead of a cloud provider going down, the defect happened on the physical servers and mainframes Chase owns and operates inside its own data centers. The bug bogged down how those internal servers handled incoming and outgoing transaction requests, causing severe delays in loading balances, processing branch and ATM activity, and approving transfers with outside banks.
Both JPMorgan Chase and federal law enforcement confirmed there was no evidence of hackers, ransomware, or malicious activity. Sources also noted the incident was not caused by third-party cloud providers like Amazon Web Services or Microsoft Azure. And although the glitch occurred shortly after a global Microsoft outage, an FAA telecommunications failure, and a separate Optimizely malicious code attack, officials confirmed the incidents were unconnected.
The Real Ripple Effect
News coverage leaned heavily on Downdetector, which only flags an outage when a large volume of users manually submit error reports at the same time. Outage trackers record user complaints rather than server status — which created the false impression of a nationwide, multi-bank crash. Customers at Bank of America, Wells Fargo, U.S. Bank, Capital One, and Truist reported errors on the tracker, even though those banks confirmed their own internal networks were operating normally.
- Root cause: A software defect in JPMorgan Chase's on-premise hardware systems, traced to a software release rolled out that morning.
- No cyberattack: Chase and federal officials found no evidence of hacking, ransomware, or malicious activity.
- Why it spread: Instant transfers require both banks to respond in real time. When Chase's servers stalled, so did every transaction with Chase on either end.
- Why it looked bigger: Downdetector counts user complaints, not server status — so healthy banks got flagged too.
- Resolution: Chase fixed the bug Monday evening and said customer accounts and funds remained secure throughout.
Why Black-Owned Banks Weren't Affected
Black-owned banks — such as OneUnited Bank, Citizens Trust Bank, and Industrial Bank — run on their own independent core banking systems. A software bug on Chase's physical servers cannot spread to or crash another bank's internal network. During the glitch, customers at these institutions could still check balances, deposit checks, and send money to other people at their own bank without trouble.
There is one caveat. If a customer at a Black-owned bank tried to send a Zelle transfer, ACH payment, or wire to someone with a Chase account on Monday afternoon, that specific transaction would have stalled while waiting for Chase to answer. But every other function worked normally. The institution itself was never down.
The reason Black-owned banks didn't dominate outage headlines comes down to scale and visibility. National banks like Bank of America and Wells Fargo have tens of millions of customers, meaning thousands of people happened to be sending money to Chase accounts at the exact same moment and flooded Downdetector with complaints. Community and Black-owned banks have much smaller customer bases, so isolated delays on Chase-bound transfers did not generate enough simultaneous reports to trigger public outage alerts. Media coverage also focused on the seven megabanks that co-own Zelle's operator, Early Warning Services — Chase, Bank of America, Wells Fargo, Capital One, PNC, Truist, and U.S. Bank.
When Black-Owned Banks Can Be Affected
Black-owned banks are insulated from outages caused by another single bank, but they are not immune to every kind of failure. Most community and Black-owned banks outsource their backend software and mobile apps to major third-party fintech vendors like Fiserv, FIS, or Jack Henry. If one of those core providers experiences a nationwide server crash, hundreds of community banks — including Black-owned banks — can lose online banking access at the same time. All U.S. banks also rely on central clearing networks like Zelle, Fedwire, ACH, and card networks like Visa or Mastercard. If the Federal Reserve's payment system or a major card network suffers a nationwide outage, transfers and card swipes stall across every bank regardless of size or ownership. And if a major cloud host like AWS or an internet backbone provider like Cloudflare goes down, any bank app hosted on that infrastructure can temporarily go offline.
In other words: a nationwide outage only reaches a Black-owned bank if it breaks the shared layer underneath — the core vendor, the payment rail, or the cloud. A bug inside one megabank's own servers stays inside that megabank. On November 16, that distinction was the difference between a headline and a normal Monday.
No Ads. By Us. For Us.
This article was made possible by readers like you. We hope it inspired you to support Emerald Book, so we can continue producing content like this.
We will never show you ads, sell your data, or require a subscription to consume our content. Your gift helps us keep the truth accessible.
Click the Support button to give a gift of any amount today.
Thank you for making this work possible.