Key takeaways
- Chase drew roughly 5,000 Downdetector reports at the peak of Monday's outage, far more than Bank of America, Wells Fargo or U.S. Bank.
- Chase said the problem was a technical issue, not a cyberattack, and that customers still had access to their accounts and funds.
- If a transfer goes wrong, federal Regulation E rules give you 60 days after your statement to report the error to your bank.
In this story 4 sections
Customers of several of the largest US banks had trouble logging in, checking balances and moving money on Monday, Nov. 16, in a bank outage today that hit Chase hardest. User reports on Downdetector, which tracks problem reports from the public, began climbing Monday morning and peaked in the early afternoon ET, when Chase alone drew roughly 5,000 reports.
JPMorgan Chase (NYSE: JPM) blamed a technical problem. A Chase spokesperson said in statements to news organizations that "some transactions are taking longer than usual to complete," that customers "still have access to their accounts and funds," and that the issue was not cyber related. The bank did not give a cause beyond that or say when every service would be back.
Which banks were affected
Chase drew far more reports than any other bank. Smaller but notable spikes showed up for:
- Bank of America (NYSE: BAC): more than 1,500 reports.
- U.S. Bank, owned by U.S. Bancorp (NYSE: USB): several hundred reports.
- Wells Fargo (NYSE: WFC): several hundred reports, with some customers saying they could not sign in online.
- Zelle: several hundred reports.
Downdetector counts are self reported and show where people are complaining, not how many accounts were hit. None of the banks said how many customers were affected.
A notice on Wells Fargo's website Monday afternoon told customers they could still reach their accounts through ATMs, branches and customer service. By late afternoon the bank's homepage no longer showed an alert. Bank of America and U.S. Bank had not issued public statements as of mid afternoon ET.
Is it a hack?
Chase said no, describing the problem as a technical issue rather than a cyberattack. No bank has said the outages share a single cause, and there is no public evidence yet linking them. Keep in mind that a transfer between two banks, including a Zelle payment, can fail when either bank has a problem, so a Chase outage can also show up as trouble for people who bank elsewhere.
What to do if your bank is down
- Do not keep resending a payment. A transfer that looks stuck may still go through once systems catch up, and sending it again can leave you with two payments. Check your pending transactions first.
- Use the channels that still work. ATMs, branches and the phone number on the back of your card often keep running when the app or website fails.
- Watch for fake "your account is locked" messages. Scammers use big outages to send texts and emails that pretend to come from your bank. Never sign in through a link in a message; open the app or type the bank's web address yourself. Our guide to spotting a scam email lists the red flags, and how to report a scam covers where to send it.
- Check your statement once service returns. If a transfer went to the wrong place, posted twice or never arrived, federal rules give you time to fix it.
Your rights if a transfer goes wrong
Under the Consumer Financial Protection Bureau's Regulation E error rules, an incorrect or missing electronic transfer counts as an error. You generally need to notify your bank within 60 days after it sends the statement that first shows the problem. The bank then has 10 business days to investigate, or up to 45 days if it gives you a provisional credit for the amount within those 10 business days. The CFPB also explains how to get money back when funds go missing from an account.
Write down what you tried and when, and keep screenshots of error messages. They make a dispute easier if a payment does not land.
This is a developing story. For more on outages and online safety, see our tech section and our recent report on the Microsoft outage.
Sources
Share this story
Spotted an error? Tell us


