Back to Home
    Operations

    Chase's 9-Hour Outage Slowed Payments at Other Banks Too — How to Protect Your Payroll

    November 18, 2026 American Business Center Editorial Team
    Chase's 9-Hour Outage Slowed Payments at Other Banks Too — How to Protect Your Payroll

    On Monday, November 16, thousands of business owners logged in to pay staff, send wires, or move money and found their bank wasn't cooperating. A software bug at JPMorgan Chase slowed transactions for roughly nine hours, and the delays spilled over to customers at other banks and to Zelle payments involving Chase accounts.

    Chase says the problem is fixed and that it was not a cyberattack. But restored service does not guarantee every delayed payment landed where it was supposed to. Here is what happened, what to check in your accounts this week, and how to make sure the next outage does not leave your payroll stuck.

    What Happened on November 16

    Based on reporting from NBC News, the Associated Press and outage trackers, the day unfolded like this (all times Eastern):

    • About 9:30 a.m.: Problem reports for Chase begin appearing on Downdetector.
    • Around noon: Reports spike, many about logging in to online banking. Some customers say branch staff told them their systems were down too.
    • 1:50 p.m.: Downdetector shows more than 4,600 reports for Chase, plus smaller numbers for Bank of America, U.S. Bank and Wells Fargo, according to NBC.
    • About 4 p.m.: Chase says the cause is a software bug in its on-premise hardware systems, that it is not cyber-related, and that it is not a systemic issue.
    • About 6:30 p.m.: A Chase spokesperson says transactions are posting normally again.

    An FBI official cited by Fox Business said the disruption traced back to a software release Chase rolled out earlier that Monday. Chase said customers kept access to their accounts and funds throughout, but some transactions took longer than usual to complete.

    Why Customers at Other Banks Felt It Too

    Chase is the largest U.S. bank by assets and sits on one side of an enormous share of payments. When its processing slowed, any payment moving to or from a Chase account slowed with it, even if the other bank's systems were running fine.

    That is exactly what the other institutions reported. U.S. Bank said its systems were not directly affected, though Zelle payments with other banks could be delayed. Zelle said its network never went down; the slowdowns came from issues at participating banks. Bank of America and Citigroup reportedly had no problems with their own services, but their transactions with Chase slowed.

    For a small business, the lesson is uncomfortable: your bank does not have to fail for your payments to stall. If your customers, vendors or employees bank with Chase, their problem became yours.

    What to Check in Your Accounts This Week

    Several outlets covering the outage noted that some delayed payments could take another business day to appear. Before the week is out:

    1. Reconcile before you resend anything

    If a payroll run, ACH payment, wire or Zelle transfer looked stuck on Monday, do not send it again until you confirm its status. Many transactions were delayed, not failed. Resending can create duplicate payments once the backlog clears, and pulling duplicate money back from an employee or vendor is awkward and slow.

    2. Match every expected deposit

    Compare incoming payments from Monday and Tuesday against your invoices, card processor settlements and payment app records. Note anything missing or doubled and contact your bank using the number on your card or the bank's official website.

    3. Talk to anyone waiting on money

    If employees or vendors were paid late, a short note explaining the bank-side delay heads off calls and protects relationships. If a vendor charged you a late fee because a payment was stuck, ask them to waive it and keep your bank records as proof.

    4. Warn your team about outage scams

    Scammers use big outages as cover. Expect emails, texts and calls claiming your account is "on hold" and needs to be "verified" or "restored." Chase says it will not ask for your password, one-time codes or remote access to your computer. Anyone on your team who handles money should hang up and call the bank directly if contacted.

    Know Your Protections, and Their Limits

    Many owners assume business accounts get the same protections as personal ones. They often don't. Federal Regulation E, which governs error resolution for electronic transfers, is written for consumer accounts. Business accounts are mostly governed by your deposit agreement and commercial banking rules, which typically give you fewer protections and shorter windows to report problems.

    Practical takeaway: review your bank statements quickly after any disruption, report discrepancies in writing, and keep a record of every call. If you run business transactions through a personal account, now is a good time to separate them. Our guide to opening a business bank account walks through what to look for, including how each bank handles errors and outages.

    5 Ways to Protect Your Business From the Next Outage

    This was not an isolated event. It followed a major Microsoft 365 outage on November 12 and a nationwide flight ground stop on November 13. You cannot prevent these failures, but you can make sure one company's bad software update does not stop your business.

    1. Keep a second business bank account

    A backup account at a different, unrelated bank, funded with enough to cover one payroll or your most critical bills, gives you a way to pay people if your primary bank stalls. Credit unions and community banks run on different systems from the big national banks.

    2. Run payroll earlier than you need to

    If your provider debits your account two days before payday, consider funding it a day earlier during busy periods. A one-day buffer turns a bank outage from a crisis into an inconvenience. Ask your payroll provider what happens if a funding debit fails, and how fast they can retry.

    3. Hold a cash cushion you can reach

    Even a small reserve, held separately from your operating account, covers urgent costs if transfers are frozen for a day. Your profit and loss statement can help you estimate what one week of essential expenses actually costs.

    4. Offer customers more than one way to pay

    If you rely heavily on Zelle or a single processor, a slowdown hits your incoming cash immediately. Accepting cards through a processor plus at least one alternative payment method keeps revenue flowing when one rail slows down.

    5. Write a one-page outage plan

    List who to call at your bank and payroll provider, which bills must go out on time, and how you will reach staff and key vendors. Keep it somewhere other than the systems that might go down, such as a printed copy or a phone note. It is also worth asking your agent whether your business insurance covers losses from third-party technology outages; many policies don't unless you add that coverage.

    The Bottom Line

    Chase's outage lasted most of a business day, and it showed how one bank's software update can ripple out to customers at other banks and to payment apps. Your money was not lost, but some of it may still be out of place. Reconcile your accounts before resending anything, warn your team about follow-on scams, and use this as the push to set up a backup account and a simple outage plan before the next one hits.

    Photo by NordWood Themes on Unsplash

    Looking for Business Funding?

    Compare top business loan options tailored to your specific needs

    Compare Business Loans

    The Small Business Marketing Playbook 2026

    10-page no-fluff guide covering Google, SEO, reviews, Meta ads, and social media.

    $29

    FREE

    Free Marketing Playbook 2026

    $29 FREE