Chase says it is working on an online banking issue as customers of several US banks report problems
Chase said in a social media comment on Monday that it was working to resolve an issue with online banking.[1] Newsweek reported that multiple US banks suffered outages on Monday, according to user reports on Downdetector and social media posts.[2]
This is an early record as of 2:20 p.m. Eastern on November 16, 2026, resting on the statements cited, and it will be updated as more is released.
What Chase said
Clash Report said Chase's official support account message at 12:48 p.m. ET was the only public confirmation so far from the three most-named banks.[3] A Chase spokesperson said some transactions were taking longer than usual to complete but customers still had access to their accounts and funds.[4]
WBAL-TV reported that a Chase spokesperson described the problem as a technical bug issue and not a cyber issue.[4] Chase said some customers saw an app message saying some services were not available and to try back later.[5]
What users reported
NBC Los Angeles reported that Chase, Bank of America, Wells Fargo and U.S. Bank all saw a surge in reported problems on Monday afternoon.[5] NBC Los Angeles also reported that, per Downdetector, more than 4,400 Chase customers had reported outages as of 1:35 p.m. ET, with Bank of America above 1,300, Wells Fargo at 380 and U.S. Bank above 650.[5]
Clash Report, citing the New York Post, said Downdetector logged more than 3,300 reports at Chase and about 800 combined at Bank of America and Wells Fargo.[3] Newsweek reported that some people said they could not cash checks, withdraw or transfer funds, or process cashier checks.[2] Clash Report, citing TMZ, said user reports had spiked since 9 a.m., and noted the timing was not independently confirmed.[3]
Cause and open questions
Clash Report said Bank of America and Wells Fargo support accounts had not, at the time of writing, issued a comparable acknowledgment of a systemwide outage.[3] Clash Report said no common cause or coordinated cyberattack had been confirmed.[3] It also said no official statement had tied the problems to a shared vendor, a cloud provider or a payments processor.[3]
WBAL-TV reported that a Microsoft outage began on Friday and lasted for hours.[4] Clash Report said no evidence had been presented that the Microsoft outage and an FAA ground stop were connected to the Monday banking reports.[3] Newsweek reported it was not immediately clear what caused the outages or when services would be fully restored.[2]
The record
- Event type
- Other[3][4][2]Stated by Clash Report, official account, Nov 16, 2026
- Means
- Not reported[3][4]
- Target type
- Business or retail[4][2]
- Occurred, start
- Nov 16, 2026[2]Stated by Newsweek, witness account, Nov 16, 2026
Each value is what a cited source stated, with its source number. Where sources give different figures, the latest official account is listed first and every other figure is listed with it. A figure for one part of an event, such as one strike in a campaign, is listed as that part and never as the total.
Case and outcome record
| Date | Stage | Who | Court, office or agency | As the source states it |
|---|---|---|---|---|
| Nov 16, 2026 | Incident | Online banking outages reported at several US banks on Monday. Chase said it was working to resolve an online banking issue and described it as a technical bug issue, not a cyber issue. No common cause or coordinated cyberattack has been confirmed, and the cause was not immediately clear.[1][3][2][4] |
One row per stage for each person, as sources report it. A stage a source only expects is not listed until it happens.
IPR records what each source says and who said it. A cited statement shows that a source said it, not that it is true. Hover a number to see the exact words quoted from that source. See something wrong? Use a flag to report it.