top of page

Chase Says It Was a Bug, Not a Hack. Zelle's Network Is Owned by the Banks It Spread To. Three Outages in a Week, and None of Them Was a Cyberattack

Writer: Patrick Duggan
Patrick Duggan
4 minutes ago
4 min read

If your paycheck, rent or payroll runs through one bank and one payment app, set up a second account at an unrelated bank this week and move a small buffer into it. On Monday, November 16, 2026, customers of Chase, Bank of America, Wells Fargo and U.S. Bank reported they could not move money, and none of that was an attack. It was a single point of failure doing what single points of failure do.



What the banks have said


Chase was hit hardest: nearly 4,800 Downdetector reports as of 2 p.m. Eastern, according to CBS News. A Chase spokesperson said, "Due to a technical issue, some transactions are taking longer than usual to complete," that customers "still have access to their accounts and funds," and, per CBS, that it was a technical bug and not a cyber issue. AP reports Chase said the problems were not the result of a cyberattack.


Bank of America, Wells Fargo and U.S. Bank customers reported problems too. U.S. Bank said its systems were not directly affected but that Zelle payments to other institutions might be delayed. Zelle said its service was operating as it should and that an issue at the financial institutions may be delaying payments. Bank of America and Wells Fargo had not given a cause by Monday afternoon, and no bank had said when service would be fully restored. AP also reported that Bank of America and Citigroup told it they were not having issues, while CBS and Yahoo Finance carried Bank of America complaints, so the picture for that bank is mixed.


Mike Chapple, a cybersecurity expert at the University of Notre Dame, told AP it "appears to stem from a technical issue at Chase" that reached other banks "through their shared payment networks." That is his reading, not a bank's statement, but it fits everything the banks did say.



The connected part


Zelle runs on a network operated by Early Warning Services. Early Warning is owned by seven banks: Bank of America, Capital One, JPMorgan Chase, PNC, Truist, U.S. Bank and Wells Fargo. So the rail that carries money between the biggest U.S. banks is owned by those same banks, and when the largest of them has a bad day, the delay shows up at the others. Nobody broke in. The system is simply connected the way it was built to be.


Monday was the third such failure in about a week. A Microsoft outage took down Outlook and Teams late last week; Microsoft called it a technical issue not linked to a cyberattack (outlets disagree on whether it started Thursday or Friday). On Friday the FAA stopped flights nationwide after routers were overloaded, per CBS. A cloud mail service, an air traffic network and a bank payment rail: three different industries, the same shape. One shared component fails and everything downstream of it fails at once.



Not every outage is an attack


Security people say "confidentiality, integrity, availability," and then spend almost all their attention on the first two. Monday was an availability failure, and availability does not need an adversary. A bad software release, an expired certificate, a full disk or a router running out of memory takes a service down just as thoroughly as ransomware does, and from the customer's side it looks the same. The first statement a company makes, "it was not a cyberattack," is a claim about cause made before the investigation has finished.



Be calm now, stay suspicious later


Take the banks at their word today, and stay suspicious over the longer term. First statements are made in the first hours, and root causes sometimes change: what was announced as a glitch has, in other incidents, later turned out to be a compromised vendor, a stolen credential or an insider, and the correction arrives weeks later in a filing nobody reads. Watch for the post-incident report, a regulator's notice or a change in the bank's story. Meanwhile the outage itself is the attack surface: when millions of people are confused about whether their money is safe, scammers send texts and emails saying "verify your account to restore access" with a link. Your bank will not text you a link to fix an outage. Go to the app or type the bank's address yourself, and treat any message about Monday's problem that asks you to log in, confirm a code or move money as fraud until proven otherwise.



What to do


For people: keep a second account at an unrelated bank, with enough in it to cover a few days. Do not rely on one instant-payment app for anything time-critical, such as rent due today. If a payment was "sent" during the outage and has not arrived, check with your bank before sending it again, so you do not pay twice. Ignore any outage-themed text or email with a link.


For small businesses: do not schedule payroll through a single bank and a single payment rail the day after a known incident without a fallback. Know who you would call and how you would pay people if your bank's online banking were down for a day.


For anyone running systems: write down which of your critical services share a component you do not control, such as a cloud region, a DNS provider, a payment network or an identity provider, and test what happens when that one piece is gone. The question is not whether you will be attacked. It is what fails at the same time as everything else.



What is not known


The technical cause at Chase beyond "technical issue" and "bug." Whether Bank of America, Wells Fargo and U.S. Bank problems came entirely from the Chase issue or partly from something of their own. When full service returned. How many payments were delayed or failed.



Sources


CBS News, "Major U.S. banks report widespread service outages," by Megan Cerullo, updated 4:52 p.m. EST November 16, 2026. AP report as carried by WBAL-TV, updated 4:10 p.m. EST November 16, 2026. 24/7 Wall St. via Yahoo Finance, November 16, 2026. Statements quoted are from Chase, U.S. Bank and Zelle spokespeople as reported by those outlets; the shared-network explanation is Mike Chapple's, University of Notre Dame, as reported by AP.




Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page