Chase Software Glitch Disrupts Payments, Spilling Over to Other US Banks
Left 47%
Center 16%
Right 37%
9 left · 3 center · 7 right
What happened
On Monday, November 16, 2026, JPMorgan Chase, the largest U.S. bank, experienced a nationwide technical problem that slowed or blocked some consumer transactions online and at branches for several hours. The bank said a “temporary issue related to a software bug in on‑premise hardware systems” caused some payments and transfers to be delayed, while stressing that customers retained access to their accounts and funds and that there was “no evidence this is cyber‑related.” Because Chase is deeply embedded in shared payment networks, customers at other major banks — including Bank of America, Wells Fargo, U.S. Bank and users of the Zelle payment service — reported problems mainly when they tried to transact with Chase accounts. Regulators and, according to one FBI official quoted by Fox Business, federal investigators engaged quickly, and by late Monday afternoon Chase and outage trackers such as Downdetector were reporting that services were returning to normal, with complaint levels back to baseline by early Tuesday. The disruption followed separate, recent technical failures at Microsoft, the Federal Aviation Administration and United Airlines, which also were publicly described as non‑cyber incidents.
Sourcing check · Mostly on the record · 19 articles
15 of 17 articles cite a named source for the story. It was on the record from the first report.
What these terms mean and how they're counted
- On the record · names a source 15 of 17
- On the record means the article cites a source by name for the story's main claim: a person, or an institution speaking officially, such as a company statement or a named agency's spokesperson. The opposite is an unnamed source. The count is how many of the counted articles cite at least one such source; the names are everyone named across them, each once however the articles spell it. Here: JPMorganChase, J.P. Morgan-Chase Bank spokesperson, Chase Bank, US Bank spokesman, Capital One and Chase spokesperson
- Primary evidence · cites a document or data 0 of 17
- Primary evidence means the article cites a record you could check yourself: a court filing or ruling, a dataset or report, a recording or transcript, an official statement or press release, market data. A quote is not a document. The count is how many articles cite one. Here: None cited.
- Credits another outlet 0 of 17
- The article says the story comes from another outlet's reporting (“first reported by Reuters”). Those articles relay the story; they are not independent confirmation. Here: Each article presents its own reporting.
- Unnamed sources 2 of 17
- The main claim is attributed to people who are not identified: “people familiar with the matter”, “officials said”. The count is how many articles do this.
- How it developed
- When the first report landed and whether it named anyone; when the first named source and the first document appeared. Here: First report Nov 16, 15:58 UTC by Daily Wire, naming its source.
- Not counted 2
- Opinion, analysis and video pieces, and articles too short to assess. Every count above is out of the counted articles. An article republished under a new headline is one article.
This is about who is cited, not whether the story is true. Each source below says what it names. How we count
Omitted — what each side leaves out
Unpacked
The biggest gap is about what, concretely, went wrong inside Chase. Right-leaning Fox Business reports an FBI official’s claim that the disruption was traced to a software release rolled out Monday morning, but left-leaning reports stick to Chase’s vaguer language about a “software bug in on‑premise hardware systems” without the deployment detail. A reader who never hears that it was a fresh software rollout may see this as a mysterious latent flaw rather than a change‑management failure with clearer accountability.
A secondary pattern is in word choice. Left‑leaning coverage tends to call the incident a “technical issue,” “glitch” or “temporary issue,” while right‑leaning outlets talk about a “meltdown” and “banking chaos.” Both describe the same hours‑long disruption, but the first frame invites seeing it as a controllable IT problem, while the second makes it feel closer to a systemic scare.
Across both sets of outlets, one question goes unanswered: how many transactions actually failed or were delayed, in dollar or volume terms, and how does that compare to a normal day at Chase?
Bottom line
Right-leaning Fox Business reports, via an FBI official, that Chase’s outage was triggered by a software release pushed on Monday morning, a specific root cause missing from most left-leaning stories that refer only to a generic “software bug” while focusing on broader concerns about fragile tech systems.
The receipts — 4 facts one side's coverage lacks
- An FBI official told Fox Business the disruption was traced to a software release Chase rolled out earlier Monday that affected a subset of its systems.
- Regulators contacted affected big banks “immediately” and quickly determined the problem was contained and service restoration was in progress.
- Experts warned that criminals would likely exploit outage anxiety with phishing and urged customers to screenshot failed transactions and later seek fee reversals.
- A former assistant Treasury secretary noted that the Federal Reserve conducts worst‑case‑scenario drills and said the real risk would be if people lose trust and start doubting the banking system.
The Left View
Left-leaning coverage centers Chase as the clear origin point of the disruption and emphasizes that other banks’ core systems were generally functioning, with problems arising mainly in transactions that touched Chase or ran over shared rails like Zelle. Outlets such as NBC News, the Guardian, CBS News and the New York Times highlight banks’ and regulators’ assurances that the issue was contained, not “systemic,” and that there was no sign of a cyberattack, while still stressing how the episode, alongside the recent Microsoft and FAA outages, has “shaken public confidence” and illustrates the “complexity and fragility” of critical digital infrastructure. They foreground official statements that regulators contacted affected banks “immediately” and quickly assessed that restoration was underway, framing this as evidence of oversight but also of how dependent daily life is on a few large providers. Several pieces devote space to consumer protection and security advice, warning that scammers may exploit outage anxiety, urging customers to document failed transactions and seek fee reversals, and cautioning against phishing emails purporting to be from banks. The tone is generally calm but worried, using words like “glitch,” “technical issue” and “bug” while using expert commentary to argue that repeated non‑cyber failures still pose systemic risk.
The Right View
Right-leaning outlets describe customer impacts in more dramatic terms, with phrases like “meltdown,” “banking chaos” and “widespread disruptions,” while still relaying Chase’s statement that a software bug, not a cyberattack, was responsible. Fox Business adds a notable detail from an FBI official that the disruption was traced to a software release Chase rolled out earlier Monday that affected a subset of its systems, reinforcing that the origin was in‑house change management rather than an external threat. Coverage in the Daily Wire, New York Post, Breitbart and OAN leans on Downdetector spikes and social‑media anecdotes about failed withdrawals, blocked cashier’s checks and error messages to illustrate public frustration and the appearance of multi‑bank trouble. Some reporting raises the possibility that recent outages in other sectors share underlying components or dependencies, quoting one cybersecurity expert who suggests the breadth of problems implies interconnected systems, while a former Treasury official is cited to warn that the real danger would be a loss of trust in the banking system. Right-leaning pieces also stress that many banks, as well as Zelle, said their own systems were “operating normally,” but this clarification tends to appear lower in the stories than the broader language about major-bank outages.
Our Take (balanced)
From the left-leaning side, the strongest argument is that even a non‑cyber, bank‑specific bug can ripple widely through shared payment networks and, when combined with outages at Microsoft and the FAA, exposes how “complex and fragile” core digital infrastructure has become; this view is supported by concrete examples of how a single technical fault at Chase generated error reports across multiple banks and services. From the right-leaning side, the strongest contribution is the more specific causal account — via an FBI official — that ties the outage to a software release deployed that morning, underscoring that ordinary operational changes at a dominant institution can quickly become a national issue and that maintaining public trust is as critical as the code itself. The unresolved tension between these perspectives is how to interpret the incident’s meaning: whether it is mainly a contained operational failure at one bank that demonstrates existing resilience, or a warning sign that the growing interconnection and concentration of financial and tech systems are outpacing institutions’ and regulators’ ability to manage cascading failures.
19 sources
- Chase says transactions back to normal after outage online and at some branches
- Customers report difficulty accessing online Chase accounts
- Chase, Bank of America, Wells Fargo customers report trouble accessing accounts
- Chase Bank says operations are back to normal after ‘bug’ disrupts transactions
- Customers report difficulty accessing online services at major US banks
- Chase software bug wreaks havoc on online banking
- JPMorgan Chase says temporary software bug is affecting consumer banking
- Customers report service outages at major US banks
- Chase Bank Resumes Normal Operations After ‘Software Bug’ Disrupted Transactions
- What May Have Set Off The Meltdown At Major U.S. Banks
- Big bank customers report outages; JPMorgan Chase blames software bug with potential ripple effects
- JPMorgan Chase systems recovering following hourslong nationwide technical outage
- Banking users report trouble accessing online services for Chase, Bank of America, Wells Fargo, others
- Tech Glitch at JPMorgan Chase Causes Banking Chaos Across Country
- JPMorgan Chase says in-house software issue impacted service — and possibly other banks
- A technical issue at JPMorgan Chase triggers online banking delays for major US banks
- Customers at nation's largest banks report difficulty accessing accounts
- Widespread service outages at major U.S. banks appear to be over
- Details on widespread outages reported by major U.S. banks
More stories
The week's bottom lines, in your inbox
One email a week: the five stories that mattered and what they actually mean. Free.