Economics

Chase's bug broke other banks, and most coverage missed that part

On Monday, Chase, Bank of America, Wells Fargo, and Capital One all went down at roughly the same time. Most outlets treated this as a multi-bank coincidence. The actual story, named by Wired and confirmed by AP, is that a JPMorgan Chase software bug in shared infrastructure took down institutions that had nothing wrong with their own systems. That distinction matters: if your bank failed because of someone else's code, the accountability question points somewhere most coverage never looked.

Framing Spectrum

JPMorgan Chase software bug triggers online banking outages at major US banks

8 sources · hover a dot to see coverage

LeftCtr-LeftCenterCtr-RightRight

What happened

On Monday, November 16, 2026, customers at Chase, Bank of America, Wells Fargo, and Capital One reported widespread inability to access online accounts or withdraw funds. Downdetector logged thousands of complaints across all four institutions within a similar window. JPMorgan Chase acknowledged a 'software bug' in its hardware systems and said it was working to fix the issue. Chase shares fell more than 2.4% on the day. The AP and Wired both reported that the outage at competing banks traced back to JPMorgan Chase's infrastructure, not to faults at those banks themselves. No cyberattack was confirmed. No customer funds were reported lost. That is the wire version. Fourteen outlets covered it. What separates the coverage is whether any of them asked why a bug at one bank could take down three others.

Wired named the shared-infrastructure problem; almost no one followed

Wired's headline, 'The Bank Outage May Have Nothing to Do With Your Bank,' is the only one in this set that names the structural finding directly. The piece explains that the outage at Bank of America, Wells Fargo, and Capital One originated in JPMorgan Chase's systems, not in any fault at those institutions. AP's straight news report confirmed the same mechanism. Neither outlet was picked up or amplified by the left-leaning or right-leaning outlets in the coverage set, which continued framing the story as a multi-bank simultaneous failure rather than a single-point-of-failure event with a known origin.

Fox News widened the frame to a national tech crisis narrative

Fox News ran the story under 'America hits a tech wall as outages cripple email, ground flights and disrupt major banks,' connecting Monday's banking disruption to a recent Microsoft 365 outage and an FAA ground stop. Fox Business stayed narrower, leading with the 2.4% drop in financial stocks and naming all four affected banks. The two outlets reached different readers with different stakes: one got a systemic-fragility story, the other got a market-impact story. Neither asked about JPMorgan Chase's role as the originating infrastructure provider.

Quartz published five explainers and reported none of the news

Quartz produced five pieces in response to the outage: backup payment methods, federal consumer protections, how to check whether a transfer went through, how to read payment statuses, and a FDIC versus bank-failure explainer. All five are useful. None of them names JPMorgan Chase, the software bug, or the shared-infrastructure finding. This is a clean example of a publication converting a news event into evergreen utility content without reporting the event itself. Readers who arrived via Quartz left knowing their rights under federal law and not knowing whose code caused the problem.

What one side told you that the other didn't

One bug at Chase took down three rival banks. Most outlets skipped that.

The shared-infrastructure angle appears in two outlets: Wired's headline names it explicitly, and AP's report confirms it. The remaining twelve outlets, including CNN, Forbes, Fast Company, Fox News, and Fox Business, framed the story as simultaneous outages at multiple banks, a framing that implies parallel failures rather than a single cascading one. The difference is not cosmetic. A single point of failure in shared financial infrastructure is a systemic risk story. Four banks having a bad Monday is a consumer inconvenience story. Twelve outlets wrote the second one.

Nobody asked why Chase infrastructure runs inside competing banks.

If JPMorgan Chase's software bug disrupted Bank of America, Wells Fargo, and Capital One, those institutions depend on Chase-operated systems for some part of their customer-facing operations. No outlet in this set reported what that dependency is, how common it is, or whether regulators have visibility into it. Forbes confirmed the bug existed. AP confirmed it caused delays at other banks. The question of what contractual or technical relationship makes that possible went unasked across all fourteen outlets. That is the story underneath the outage story.

CNN covered Chase. It did not cover the infrastructure finding.

CNN's piece is headlined 'Thousands of Chase Bank customers report trouble with online banking services,' which frames the story as a Chase-specific customer experience. The Wired and AP reports, published in the same news cycle, had already established that the disruption extended to three other major banks via Chase's infrastructure. CNN's framing is not wrong, but it is incomplete in a specific way: it removes the systemic dimension and leaves readers with a single-bank story about a four-bank event.

Futurism asked the right question and did not answer it.

Futurism's headline, 'Wait, Why Did Every Major Bank Just Go Down?', is the only one in the set that frames the event as a question requiring explanation. The excerpt, 'The internet just can't catch a break,' suggests the piece did not pursue the infrastructure answer that Wired and AP had already reported. Asking the right question and then not reporting the answer is its own kind of gap. The explanation existed in the same news cycle. It just wasn't in Futurism's piece.

What to watch

Chase has not disclosed which specific systems the bug affected or which third-party banks depend on that infrastructure. If a congressional banking committee or the OCC requests documentation of the shared-infrastructure arrangement within the next two weeks, watch whether outlets that missed the dependency angle pick it up then, or whether they continue covering regulatory response as a Chase-only story.

4 min read8 sources4 framing gaps flagged

See how outlets across the political spectrum framed this differently — and what each side left out.