1. What Happened Today: Four of America’s Biggest Banks Went Down at Once
On Monday morning, November 16, 2026, customers of several of the largest banks in the United States found they could not log in, see their balances, or move money. JPMorgan Chase was hit hardest. Bank of America, Wells Fargo, and U.S. Bank also drew a wave of complaints, and the Zelle payment network appeared in the same cluster of reports.
Complaints about Chase on the outage-tracking site Downdetector started climbing around 7 a.m. Pacific Time and passed 2,000 by about 8 a.m. Pacific. By about 10:50 a.m. Pacific, Chase had nearly 20,000 reports. Bank of America had nearly 2,000, U.S. Bank almost 1,000, and Wells Fargo nearly 500, according to Downdetector figures reported by GV Wire. CBS News, in an update issued at 1:30 p.m. Central, said nearly 4,800 users had reported problems with Chase as of 1 p.m. Central. The counts moved through the day as reports rose and fell — and it is worth remembering that Downdetector counts user-submitted reports, not a verified number of affected customers.
The problems were not limited to the four biggest names. Downdetector also showed reports for TD Bank, Regions, USAA, Capital One, Citi, American Express, Fifth Third Bank, Navy Federal Credit Union, and Truist, alongside Zelle. JPMorgan Chase is the largest bank in the United States, so when its online banking stumbles, millions of businesses and households feel it within the hour.
For a small business, the timing could hardly be worse. Monday morning is when payroll runs are checked, supplier payments go out, and weekend card takings are reconciled. A bank app that will not load does not just inconvenience one person — it freezes the money movement a business runs on.
2. What Each Bank Is Saying — and What Is Still Unknown
Chase has confirmed the problem and says it is a technical issue, not a cyberattack. In a statement issued to 7 News Miami and confirmed to NBC Chicago, a Chase spokesperson said: “Due to a technical issue, some transactions are taking longer than usual to complete, but customers still have access to their accounts and funds. We are working to resolve this as quickly as possible.” Chase Support also told customers on X that it was working to resolve an issue with online banking.
Wells Fargo posted a notice on its website that online banking was temporarily unavailable, and pointed customers to ATMs, branches, and its 24-hour phone line. Bank of America declined to comment. Zelle told NBC Chicago that the Zelle reports were, in its words, “a Chase issue” — a reminder that when one big bank’s systems falter, the payment rails connected to it wobble too.
As of early Monday afternoon Pacific Time, no common cause had been confirmed for the cluster of outages, and neither Chase nor Wells Fargo had given a timeline for full restoration. Market reports said the Federal Reserve’s own payment systems — Fedwire, FedACH, and FedNow — were operating normally. Plaid, the company many apps use to connect to bank accounts, still listed a partial outage affecting Chase connections as of about 1:35 p.m. Central.
That uncertainty matters for business owners. A single bank’s technical fault is a known quantity: wait, use another channel, carry on. Several banks failing at once with no shared cause named yet is harder to plan around — which is exactly why the next section matters more than the outage itself.
3. No, This Is Not the November 17 Blackout Rumour
If you have seen social media posts claiming bank balances will be wiped and the internet shut down for three months on November 17, treat them as what they are: a rumour. A same-day fact-check confirmed that Chase and Wells Fargo have real, confirmed online-banking problems today — and that those real outages are not evidence that the November 17 claim is coming true. There is no confirmed cyberattack behind today’s outages, no banking-system collapse, and no official source supporting the wiped-balances claim.
The rumour is worth naming in plain terms because it changes behaviour. A business owner who believes their balance is about to vanish may try to move money in a panic — and a panicked transfer during an outage is exactly how duplicate payments, failed transfers, and lost records happen. Do not move money because of a viral post. Check your balance through your bank’s official app, website, or phone line, and only act on what your bank itself confirms.
The same rule applies to the outage itself: if a message, email, or text claims to be from your bank and asks you to “verify” your account or move funds because of today’s outage, assume it is a scam until proven otherwise. Outages are prime phishing season. Your bank will not ask you to move money to a “safe account” — that is the oldest trick in the book, and it works best on a day when people are already anxious about their money.
4. Why Your Business Felt It Even If You Bank Elsewhere
You do not need a Chase or Wells Fargo account to feel this outage. Modern business payments run through shared rails, and today’s disruption hit several of them at once:
- Zelle and bank-to-bank transfers: Zelle appeared in the same Downdetector cluster as the banks, and Zelle itself pointed to Chase as the source. If a customer paid you by Zelle today, or you paid a supplier that way, the money may be sitting in a queue rather than in your account.
- Connected apps: Plaid connects thousands of apps — accounting tools, invoicing software, payroll platforms — to bank accounts. Its partial outage affecting Chase connections means your bookkeeping app may show stale balances or failed syncs today even though your money is fine.
- Payroll and supplier runs: Monday is a heavy day for scheduled payments. A payment that “takes longer than usual” is still a payment that has not landed, and a supplier who expected it this morning may already be chasing it.
- Card and ATM fallbacks: Wells Fargo directed customers to ATMs, branches, and phone banking. Those channels work, but they are slow — and a queue at a branch is not a plan for a business that needs to pay ten suppliers before lunch.
The practical test is simple: before you re-send any payment today, check whether the first one actually went through. A duplicate payment is worse than a late one, because getting it back takes days of phone calls. Check the official status page or app first, then your transaction history, and only then decide whether to re-send.
5. The Pattern: Third Major US Disruption in Under a Week
Today’s bank outage is the third major technology disruption in the United States in less than a week, after the Microsoft 365 outage and the nationwide FAA ground stop. That sequence is what makes today different from an ordinary bad morning at one bank.
On November 12, Microsoft 365 and Outlook went down worldwide, locking businesses out of email, Teams, and documents for hours. On November 14, the FAA grounded flights nationwide. Today, November 16, online banking at the country’s biggest banks faltered. Officials have denied any connection between the Microsoft outage and the FAA ground stop, and no common cause has been confirmed for today’s bank outages either. There is no evidence the three events share a cause — but for a business owner, the cause matters less than the pattern.
The pattern is this: the services a small business depends on — email, flights, banking — are each run by a small number of very large providers, and each one can fail on an ordinary Monday. We have covered the same lesson three times in five days on this blog: the Microsoft 365 outage, the Claude outage, and the Workday outage that stopped payroll. Each time, the businesses that coped best were the ones with a second way to do the same job.
That is the real story of today. Not a cyberattack, not a conspiracy — a reminder that single points of failure are everywhere, and most businesses only discover them on the day they break.
6. Seven Checks to Run Today If Your Business Banked With an Affected Bank
Do these in order, and do not skip the boring ones — they are the ones that prevent expensive mistakes:
- Confirm the outage is real, from your bank: Check your bank’s official status page, app notice, or phone line — not a screenshot on social media. Chase and Wells Fargo have both confirmed problems today.
- Check what actually went through: Before re-sending any payment, look at your transaction history. A payment that is “taking longer than usual” may still land. Re-sending creates duplicates.
- Tell your suppliers and customers first: A short message — “our bank’s online banking is down today, your payment may arrive late, we are monitoring it” — buys more goodwill than silence. People forgive delays; they do not forgive being ignored.
- Use a second channel for urgent payments: ATM, branch, phone banking, or a second bank account if you have one. Keep a record of which channel you used for each payment.
- Pause automated payments until you can see clearly: If your accounting or payroll tool syncs through Plaid, check whether the sync is stale before trusting its balances. A partial outage can make your books look wrong when your money is right.
- Watch for phishing: Expect fake “your bank” messages today. Never click a link in a text or email about the outage. Go to the bank’s site yourself, or call the number on your card.
- Write it down: Note the time you first noticed the problem, what failed, and what you did about it. If a payment lands late and a supplier charges a fee, that note is your evidence.
7. How to Make Your Business Payments Outage-Proof in Seven Days
Today’s outage will pass. The lesson should not. Here is a one-week plan to make sure the next one costs you an hour, not a day:
- Day 1 — Open a second business account: A second account at a different bank is the single most effective insurance against a bank outage. Keep enough in it to cover one week of essential payments.
- Day 2 — List every payment rail you use: Bank transfer, Zelle, card, direct debit, Plaid-connected apps. For each one, write down the fallback. If the answer is “nothing”, that is the gap to close.
- Day 3 — Test the fallback: Move a small amount through your second account and your backup payment method. A fallback you have never tested is a hope, not a plan.
- Day 4 — Separate payroll from everything else: Payroll is the payment that cannot be late. Give it its own funding path and its own check — the Workday outage that stopped payroll two days ago showed what happens when the HR system and the money both depend on the same chain.
- Day 5 — Write a one-page outage script: Who tells suppliers, who tells customers, who checks the bank, who approves manual payments. One page, printed, in the office. The day of the outage is the wrong day to invent it.
- Day 6 — Review your connected apps: Check which of your tools depend on Plaid or a single bank connection. Ask each vendor what happens when the connection drops — and whether your data stays safe while it does.
- Day 7 — Schedule a quarterly resilience check: Put a 30-minute calendar reminder every three months to re-test the second account, re-check the fallback list, and confirm the outage script is still current.
None of this requires new software or a big budget. It requires deciding, while the outage is still fresh in your mind, that next time you will be the business that keeps trading while others wait on hold.
8. What to Watch Next: The Questions That Still Need Answers
As of early Monday afternoon Pacific Time, several questions remain open, and the answers will shape how seriously businesses should treat today:
- What actually caused it? Chase calls it a technical issue; Wells Fargo has not given a cause; no common cause has been confirmed across the banks. A single shared vendor, a network fault, or several unrelated faults on the same morning would each mean something different for your risk planning.
- How long until full restoration? Neither Chase nor Wells Fargo had given a timeline as of early Monday afternoon. Watch for an all-clear from your bank, not from social media.
- Will there be a post-incident report? The Microsoft outage two days ago came with an incident reference and a promised report. A clear explanation from the banks would help every business decide whether today’s problem was a one-off or a warning.
- Does this change anything about the November 17 rumour? No. Today’s real outages do not make the viral November 17 claim true. Keep watching official bank and regulator channels, and treat any message predicting wiped balances as a scam until a named, official source says otherwise.
We will update this article if the banks publish a cause or a restoration timeline. For now, the safe summary is: your money is still yours, your bank is working on the problem, and the businesses that handle today well will be the ones that checked before they re-sent, told people early, and had a second way to pay.
The Bottom Line
Chase, Bank of America, Wells Fargo, and U.S. Bank all reported online banking problems on Monday, November 16, 2026, with Chase hit hardest and Zelle caught in the same cluster. Chase says it is a technical issue, not a cyberattack, and that customers still have access to their accounts and funds. No common cause has been confirmed, and no restoration timeline had been given by early Monday afternoon. The November 17 blackout rumour is not supported by any official source — do not move money because of it.
For your business, today is a drill with real stakes: check before you re-send, tell your suppliers early, use a second channel for urgent payments, and watch for phishing. Then, this week, open that second account and write that one-page outage script. The next outage is a matter of when, not if — and the businesses that survive it best are the ones that prepared on a day exactly like today.
Want help making your business resilient to the next outage? Book a free consultation with AI Dev Expert — we help small businesses set up the systems, backups, and automations that keep you trading when a big provider goes down.
Sources: Political.org (Chase leads wave of online banking outages, Nov 16, 2026); NJ Radar Online (Major U.S. Banks Hit by Online Banking Outages, Nov 16, 2026); Men’s Journal (Chase, Bank of America, Wells Fargo, U.S. Bank Outage Widens, Nov 16, 2026, 2:10 PM EST); Parade (Are Chase, Bank of America, Wells Fargo, U.S. Bank and More Down?, Nov 16, 2026); MyNewsLA (Banking Outages Reported Across Nation, Nov 16, 2026); Candid Dragon (Chatter Check: U.S. Bank Outages on November 16, Not the November 17 Rumor, Nov 16, 2026); NBC Chicago (Is Chase Bank down? Multiple banks report online issues, Nov 16, 2026); CBS News (Major U.S. banks report widespread service outages, updated Nov 16, 2026, 2:30 p.m. Eastern, via Candid Dragon). Downdetector figures count user-submitted reports, not verified affected customers. This article is general business information, not financial advice.
Related Reading
- Microsoft 365 Just Went Down Worldwide: What the Outlook Outage Means for Your Business (2026)
- Workday Went Down and Payroll Stopped: What the HR Outage Means for Your Business (2026)
- Claude Went Down Twice in One Day: What the Anthropic Outage Means for Your Business (2026)
- One Cloud Region Went Down and Europe’s Banks Stopped Working: 7 Resilience Lessons for Your Business (2026)
- Binance Just Lost $6.3 Billion in the Largest Crypto Hack Ever: 7 Security Lessons for Your Business (2026)
