MAJOR US BANK CUSTOMERS REPORT ONLINE SERVICE PROBLEMS AS CHASE CONFIRMS TECHNICAL ISSUE DELAYING TRANSACTIONS

Customers at several major U.S. banks, including JPMorgan Chase, Bank of America, U.S. Bank and Wells Fargo, reported online banking and transaction problems on Monday, November 16, with Downdetector recording thousands of complaints. Chase confirmed that a technical issue was causing some transactions to take longer than usual and temporarily affecting certain digital services, but said customers continued to have access to their accounts and funds and that the disruption was not a cyberattack. Other banks said their core systems were largely operating normally, while U.S. Bank and Zelle indicated that some payments involving another affected financial institution could still be delayed. There is currently no verified evidence that a single technical failure or malicious actor simultaneously disrupted all of the banks appearing on Downdetector.
Customers of several of the largest banks in the United States reported problems accessing online banking and completing transactions on Monday, November 16, as JPMorgan Chase confirmed that a technical issue was delaying some transactions and temporarily affecting parts of its digital banking services. Reports of problems appeared across Downdetector for Chase, Bank of America, U.S. Bank and Wells Fargo, while some users also reported difficulty with Zelle payments, prompting concern among customers who rely on mobile banking applications for transfers, bill payments and other everyday financial activity. Chase acknowledged that it was experiencing a technical problem but stressed that customers continued to have access to their accounts and money, while several other banks whose names appeared on Downdetector said their own core banking systems were operating normally.
The disruption became visible around midday in the United States as the number of user reports began increasing rapidly on Downdetector, a website that tracks service problems using reports submitted by customers and information collected from several other sources. By around 2 p.m. Eastern Time, more than 4,700 Chase users had reported problems, while Bank of America had accumulated roughly 2,000 reports and U.S. Bank and Wells Fargo had each recorded around 1,000 reports, according to figures cited by FOX Local. Those numbers represented reports submitted by users rather than a verified count of every customer affected, but the simultaneous surge across several financial institutions was enough to trigger widespread concern and renewed questions about the resilience of the digital systems on which millions of Americans now depend for routine banking.
Chase was the most prominent bank to confirm an actual internal technical problem. In a statement issued as complaints increased, the bank said that a technical issue was causing some transactions to take longer than usual to complete, while emphasizing that customers retained access to their accounts and funds. Chase said it was working to restore normal service as quickly as possible and separately told customers through its support channels that its teams were addressing an online banking problem. Some users attempting to access Chase services also saw an in-app message stating that certain services were temporarily unavailable and asking them to try again later, providing direct confirmation that at least part of the disruption was affecting the bank’s own digital infrastructure rather than simply reflecting isolated customer connectivity problems.
Importantly, Chase also said the problem was technical rather than cyber-related. That clarification became particularly significant as online speculation grew about whether the simultaneous reports at several financial institutions might indicate a coordinated cyberattack or a wider breakdown in U.S. digital infrastructure. The Associated Press reported that Chase specifically described the disruption as a technical bug and said it was not a cybersecurity incident, while Reuters reported that there was no indication malicious actors were involved in JPMorgan’s issue and no evidence that a single software bug was simultaneously affecting all of the banks whose customers had submitted complaints. That distinction is crucial because Downdetector can show that users are experiencing problems at the same time without demonstrating that the institutions themselves are suffering from the same underlying failure.
Bank of America, U.S. Bank and Wells Fargo were among the other institutions appearing on Downdetector, but their responses indicated that the situation was more complicated than a simultaneous outage affecting every major U.S. bank. Reuters reported that the other banks it contacted said they were not experiencing significant internal disruptions, while Bank of America told news organisations that its own services were operating normally. U.S. Bank similarly said its systems were functioning, although some customers attempting to send or receive Zelle payments involving another institution could encounter delays if the bank on the other side of the payment was experiencing technical problems. This means a customer could experience what appears to be a U.S. Bank or Bank of America transaction failure even when that institution’s own systems are functioning normally, particularly when the transaction depends on another bank or an external payment network.
Wells Fargo was also listed among the financial institutions generating elevated reports on Downdetector, but there was no comparable confirmation from the bank that its core systems were suffering from a significant internal outage. That distinction illustrates one of the difficulties involved in interpreting real-time outage-tracking data. A spike in complaints can reflect genuine system failure, but it can also result from problems involving a third-party payment provider, another financial institution, telecommunications services, customer authentication systems or even confusion caused by widespread reports about another company. For customers, all of those scenarios can feel the same because the immediate experience is simply that a transfer, login or payment is not working as expected, but for determining the cause of an incident they are very different.
Zelle became an important part of the developing story because the payment service connects customers across hundreds of American banks and credit unions. Users reported difficulties involving the service on Monday, but Early Warning Services, the company that operates Zelle, said its network itself was fully operational. The company indicated that payment delays could instead occur when participating banks experience technical problems, meaning a customer whose own bank is functioning normally may still encounter difficulties when attempting to transfer money to or from an account at an institution dealing with an outage. U.S. Bank made a similar point in its response, saying that Zelle payments involving other financial institutions could be delayed even though U.S. Bank’s own systems were operating normally.
That interconnected structure helps explain why reports appeared across several bank names at roughly the same time even though only Chase publicly confirmed a significant internal technical issue. Modern electronic payments are rarely handled entirely within a single bank. A transfer may pass through multiple institutions, clearing systems, authentication services and payment networks before reaching the intended recipient, so a failure or slowdown at one point can create symptoms that appear elsewhere. If a Chase customer attempts to send money to a customer at another institution through Zelle, for example, a Chase-side delay can potentially result in complaints from both the sender and recipient even though the second bank has no internal outage. The same principle applies to other transactions that depend on interconnected financial infrastructure.
For individual customers, however, the technical distinction offers little comfort when a payment appears delayed. Digital banking has become deeply embedded in daily economic life in the United States, with customers using mobile applications to pay rent, transfer money to family members, settle bills, move funds between accounts and make time-sensitive business payments. Even relatively short service disruptions can therefore create immediate inconvenience, particularly for people who need to complete transactions before deadlines or who depend heavily on instant transfers. Chase’s reassurance that customers could still access their money was therefore important, because the available evidence did not indicate that deposits had disappeared or that customers had lost control of their accounts.
The bank’s statement also sought to distinguish delayed transactions from missing funds, an important difference during periods of widespread online concern. When users see a payment remain pending or encounter an error message while transferring money, fears can quickly spread that funds have been removed or accounts compromised. Chase said that was not the situation and emphasized that customers still had access to their accounts and money. There was no verified evidence on Monday suggesting that customer deposits had been lost, that balances had been broadly altered or that attackers had gained access to account information as part of the technical incident.
Customer reports nonetheless showed that the experience varied considerably. Some Chase users said they were unable to use certain online functions, while others reported transaction delays or notices stating that specific services were unavailable. The variation is consistent with a partial service failure rather than a complete shutdown of the bank’s operations. Chase branches, accounts and access to funds remained available, according to the bank, while some digital functions were degraded. That distinction is also why describing the event as every major American bank being completely “down” would overstate what has been confirmed.
Downdetector’s role in the story also requires context. The service is useful for identifying sudden spikes in customer complaints and can often provide an early indication that a digital platform is experiencing widespread difficulty, but its data should not be interpreted as an official measure of the total number of customers affected. Reports are voluntarily submitted, meaning people who encounter a problem are more likely to visit the site than customers whose services are working normally. A bank with tens of millions of customers can therefore generate thousands of Downdetector reports without necessarily experiencing a systemwide failure affecting every account holder.
Monday’s disruption attracted additional attention because it came only days after another major technology outage affected Microsoft services. A widespread Microsoft disruption beginning the previous week interfered with Outlook, Teams, Copilot and other Microsoft 365 products, with some government offices and businesses reporting problems. Microsoft attributed that incident to technical infrastructure issues rather than a cyberattack and said services subsequently recovered. The proximity of the Microsoft disruption to the banking reports led some users online to speculate about a connection, but there is currently no verified evidence showing that the events were related.
The United States had also experienced a major disruption involving aviation systems shortly before the banking problems, further contributing to public concern about the stability of critical digital infrastructure. News reports on Monday noted that the banking issue followed the recent Microsoft outage and problems that affected U.S. air travel. Those incidents occurred close together in time, but officials and companies have not provided evidence establishing a common cause. Treating the events as part of one coordinated attack or a single nationwide technological failure would therefore go beyond the available facts.
The concentration of major technology disruptions within a short period nonetheless highlights the extent to which modern society depends on complex digital systems. Banking, aviation, government communications, workplace software and payment networks now rely on interconnected infrastructure that can affect millions of people when even a relatively small technical component fails. Companies invest heavily in redundancy and disaster recovery precisely because interruptions can carry substantial financial and reputational consequences, but Monday’s events demonstrate that even the largest institutions remain vulnerable to technical problems.
For banks in particular, reliability is central to public trust. Customers expect financial institutions not only to safeguard deposits but also to provide continuous access to accounts. Mobile and online banking applications are no longer optional conveniences for many users; they have effectively become the primary branch through which people interact with their banks. When those services fail, customers may lose the ability to verify balances, transfer money or complete payments even when the underlying funds remain secure.
JPMorgan Chase’s scale makes any disruption particularly significant. The bank is one of the largest financial institutions in the United States and serves tens of millions of consumers and businesses. Even if only a small percentage of its customer base experiences problems, that can translate into a very large number of affected people. The bank’s systems also interact with payment platforms, other financial institutions and merchant networks, creating the potential for delays to be noticed beyond Chase’s own customer base.
That interconnectedness appears to have contributed to some of Monday’s confusion. A customer at U.S. Bank, for example, could attempt to receive a Zelle transfer from a Chase customer and experience a delay even though U.S. Bank’s own systems were functioning properly. From the customer’s perspective, the payment would appear to be a problem affecting both institutions. From an infrastructure perspective, however, the delay might originate entirely on the Chase side. This is one reason officials and banks were careful to distinguish between user-reported problems and confirmed internal system failures.
Early Warning Services’ statement that Zelle itself remained operational offered further evidence against the idea of a single nationwide payments failure. Zelle is operated by a company owned by several major financial institutions, including JPMorgan Chase, Bank of America, Wells Fargo and U.S. Bank, and its service depends on participating banks successfully processing transactions. The network can therefore remain technically available while particular payments are delayed because one member institution is experiencing problems.
Monday’s incident also underscores why financial institutions frequently advise customers not to repeatedly submit the same transaction during a service interruption. When a payment appears stuck or produces an error, repeatedly attempting the transfer can sometimes result in duplicate instructions being processed once systems recover. There was no evidence in Monday’s reporting of widespread duplicate charges caused by the current disruption, but customers experiencing delays generally benefit from checking transaction histories carefully before resubmitting transfers and from using official bank support channels rather than responding to unsolicited messages.
That final point is particularly important whenever a high-profile banking outage occurs because fraudsters often exploit public confusion. Criminals can impersonate bank employees, send fake text messages claiming that accounts are affected or direct customers to fraudulent websites designed to steal login credentials. Chase did not attribute Monday’s disruption to cybercrime, but the existence of a genuine technical problem can make fraudulent messages appear more believable because customers are already expecting communication about service difficulties.
Consumers should therefore rely on the official banking application, official websites and verified customer service numbers when checking the status of their accounts. No legitimate bank should require customers to provide passwords or complete account credentials in response to an unsolicited social media message, email or text. Customers who receive unexpected requests for login information during a widely reported outage should treat those communications cautiously.
The broader financial system continued functioning throughout Monday’s disruption. There was no evidence of a banking panic, widespread closure of branches or interruption to the underlying safety of deposits. The problem reported by Chase involved transaction processing speed and access to some online services rather than the solvency or financial health of the institution. That distinction is essential because technical service failures can generate dramatic headlines but are fundamentally different from the type of banking crisis that threatens deposits or an institution’s ability to meet its financial obligations.
Federal deposit protections were also unaffected by the technical issue. Eligible deposits at insured U.S. banks remain covered under the normal federal deposit insurance framework regardless of temporary problems with online banking applications. A customer being temporarily unable to complete a mobile transaction does not mean the underlying deposit has disappeared or lost its legal protections.
The situation nevertheless matters for businesses that rely on rapid electronic payments. Small companies increasingly use mobile banking platforms and payment networks for payroll, supplier payments and transfers between accounts. Even temporary transaction delays can affect cash flow if payments are expected at a particular time. Businesses affected by the Chase disruption may therefore need to confirm that pending transactions ultimately clear before initiating replacements.
Financial institutions typically maintain multiple layers of contingency systems, but service disruptions can still occur because of software failures, server problems, database errors or unexpected interactions between systems. Chase had not publicly identified the precise technical cause of Monday’s issue at the time of the latest reports, saying only that the bank was working to resolve the problem. Until the company provides additional details, speculation about the specific failure would be premature.
The bank also had not publicly provided a definitive estimate of how many customers were affected. Downdetector figures offer an indication of the scale of reported problems but cannot provide an exact total because many affected customers never file reports while some complaints may result from unrelated local internet or device problems. A full assessment would require internal data from Chase showing failed logins, delayed transactions and other service errors.
The same caution applies to Bank of America and Wells Fargo. Elevated Downdetector activity does not by itself establish that those banks experienced major internal outages. Reuters reported that the other banks contacted said they were not experiencing significant issues, while the Associated Press noted that Bank of America and Citigroup said their banking services were operating normally.
The discrepancy between customer reports and corporate statements is not necessarily contradictory. A customer can genuinely experience a failed payment involving Bank of America even when Bank of America’s platform itself remains functional if the transaction depends on another institution experiencing technical problems. Likewise, a user may report a Wells Fargo issue to Downdetector if a transfer involving a Chase account is delayed. Understanding those interdependencies is important when interpreting a fast-moving story involving multiple financial institutions.
News organisations initially described the event as reports of outages affecting several major banks because that was what Downdetector data showed. As banks responded, however, a more nuanced picture emerged: Chase had confirmed a technical problem, while several other institutions said they were operating normally or were primarily seeing knock-on effects involving payments to or from other banks. That progression is common in developing technology stories, where early customer reports appear before companies have completed internal assessments.
The developing information also illustrates why claims of a “nationwide bank outage” should be treated cautiously. There were widespread user reports, but there was no evidence that the entire U.S. banking network had stopped working. Customers continued to access funds, branches remained operational and core banking infrastructure continued processing transactions. The confirmed disruption was significant enough to affect thousands of reported users, but it was not equivalent to a collapse of the national financial system.
For JPMorgan Chase, the immediate priority remained restoring normal transaction processing and online functionality. The company did not provide a firm timetable in its initial public statements, saying instead that engineers were working to resolve the problem as quickly as possible. The bank’s ability to restore services quickly will determine whether Monday’s incident remains a short-lived technical inconvenience or becomes a larger customer-service issue.
Regulators may also monitor significant outages at major financial institutions because operational resilience has become an increasingly important component of banking supervision. Financial regulators expect large banks to maintain systems capable of continuing critical operations during technology failures, cyber incidents and other disruptions. A temporary technical issue does not automatically indicate a regulatory failure, but repeated or severe outages can attract scrutiny if they reveal weaknesses in a bank’s controls.
Operational risk has grown more important as banking has become increasingly digital. Decades ago, customers could conduct most business in physical branches and outages affecting an online service might inconvenience only a limited percentage of account holders. Today, millions of transactions take place through mobile devices, meaning even a short digital disruption can affect customers nationwide almost immediately.
The growth of instant payment systems has increased expectations further. Consumers accustomed to transfers arriving within seconds can become alarmed when payments remain pending for minutes or hours. Those expectations place additional pressure on banks to maintain uninterrupted service and to communicate clearly when problems occur.
Chase’s statement that customers retained access to their accounts and money was therefore a central part of its response. It signaled that the problem affected transaction processing and some online functions but had not compromised the integrity of customer deposits. The bank’s explicit statement that the problem was not cyber-related also aimed to address the most serious concerns circulating online.
The lack of evidence of a cyberattack is particularly important given the security sensitivity of the financial sector. Banks are constant targets for cybercriminals, ransomware groups and state-linked hacking operations, making any simultaneous technical disruption across several institutions likely to generate immediate suspicion. Authorities and companies generally avoid ruling out malicious activity until they have investigated, but Chase’s direct characterization of the problem as technical provides the strongest available evidence regarding the cause of its own outage.
There is also no verified evidence connecting Monday’s banking disruption with the Microsoft outage that affected Outlook, Teams and Copilot days earlier. Microsoft described its own incident as a technical infrastructure problem and did not attribute it to a cyberattack. Although the timing of the two disruptions has fueled speculation, temporal proximity alone is not evidence of a common cause.
The same caution applies to the recent U.S. aviation disruption. Reports of technology failures across different sectors can create the impression of a coordinated national event, particularly on social media, but complex infrastructure experiences unrelated failures regularly. Establishing a connection requires technical evidence, not simply the fact that events happened during the same week.
For customers still experiencing problems, the most practical step is to verify transaction status directly through official bank channels before attempting repeated payments. Customers should also retain confirmation numbers, screenshots or other records of transactions that appear delayed, particularly if the payment is time-sensitive. Those records can be useful if a bank later needs to investigate fees, missed deadlines or duplicated instructions.
There had been no broad announcement from Chase indicating that customers needed to take any special action beyond waiting for services to recover. The company said it was working on the issue and continued to reassure customers that their accounts and funds remained accessible.
The disruption is likely to prompt renewed discussion about how much of modern financial activity depends on a relatively small number of large technology systems. Banks operate their own infrastructure but also rely on payment networks, telecommunications providers, cloud services, card processors and third-party software. The resulting ecosystem is highly efficient under normal conditions but can produce cascading effects when a major component encounters difficulties.
That vulnerability does not mean digital banking is inherently unsafe. Financial institutions maintain extensive backup systems and cybersecurity controls, and most outages are resolved without customers losing money. Monday’s incident instead demonstrates how operational reliability has become part of the essential infrastructure of everyday life.
The events also illustrate why transparency during outages matters. Customers generally tolerate temporary technical failures more readily when companies explain what is happening, confirm whether funds are secure and provide regular updates. Vague or delayed communication can allow rumours to spread, especially when people cannot access services involving their money.
Chase’s early acknowledgement therefore provided an important baseline for understanding the situation. It confirmed that a genuine technical issue existed, explained its primary effect and rejected the most alarming interpretation that the bank had suffered a cyberattack.
As Monday progressed, the evidence increasingly suggested that Chase was experiencing the clearest confirmed internal disruption while many of the complaints involving other institutions could reflect interconnected transaction delays or customer-side issues. Reuters reported that other major banks said they were not experiencing significant disruptions, reinforcing the importance of distinguishing between user reports and confirmed system failures.
The situation remained developing, however, and service status could change as banks continued monitoring customer reports. Additional statements from Chase or other institutions could provide a clearer explanation of the technical cause, the total number of customers affected and the time required for complete recovery.
For now, the available evidence supports a clear but measured conclusion: thousands of customers reported problems involving several major U.S. banks on Monday, Chase confirmed that a technical issue was delaying some transactions and affecting parts of its online service, and there was no verified evidence of a cyberattack or of a single technical failure simultaneously bringing down the major banks. Other financial institutions said their own core systems were largely functioning, while some Zelle transactions could be delayed when payments involved a bank experiencing technical problems.
The incident is nevertheless a significant reminder of the central role digital banking now plays in the U.S. economy. A service disruption lasting even a relatively short period can generate thousands of complaints, affect transactions between institutions and spread concern rapidly across social media because consumers increasingly expect immediate access to their money at all times.
Whether Monday’s problem ultimately becomes a larger operational issue will depend on how quickly Chase restores full service and whether investigators or the bank identify any wider technical consequences. At the latest verified stage of the story, customers’ money remained accessible, no evidence had emerged of malicious activity, and the disruption was being treated as a technical problem rather than a threat to the safety or stability of the U.S. banking system.

