Monday, November 16, 2026Independent · Sourced · Free to Read
Subscribe
Vetted News · Preparedness · History · Religion · And More

Chatter Check: U.S. Bank Outages on November 16, Not the November 17 Rumor

Chase and Wells Fargo confirmed online-banking problems on November 16. The outages are real. They are not evidence that the November 17 rumor — wiped balances and a three-month internet shutdown — is coming true.

Almanac-style map of the United States titled Where Banks Went Down, Nov. 16, 2026, as of 5:45 p.m. CT, with the Candid Dragon dragon-eye mark and wordmark. The country is shaded to show nationwide user reports of banking problems. Red pins mark Chicago, a Downdetector hotspot, and Dallas and Irving, Texas, where a Chase branch and a Chase ATM were reported out of service. A legend lists Chase, Bank of America, Wells Fargo, and U.S. Bank. A note says the map is based on user reports via Downdetector and news coverage, not official bank data.

✅ Confirmed Scales icon Factual Verdict: Real outages, not the November 17 rumor. Chase and Wells Fargo confirmed online-banking problems today; by early evening Chase said transactions were posting normally again. That is not the same as a banking-system collapse, a confirmed cyberattack, or the viral claim that bank balances will be wiped and the internet shut down on November 17.

Almanac-style map of the United States titled Where Banks Went Down, Nov. 16, 2026, as of 5:45 p.m. CT, with the Candid Dragon dragon-eye mark and wordmark. The country is shaded to show nationwide user reports of banking problems. Red pins mark Chicago, a Downdetector hotspot, and Dallas and Irving, Texas, where a Chase branch and a Chase ATM were reported out of service. A legend lists Chase, Bank of America, Wells Fargo, and U.S. Bank. A note says the map is based on user reports via Downdetector and news coverage, not official bank data.
Where banks went down on Nov. 16, 2026, as of 5:45 p.m. CT. The nationwide shading reflects user reports to Downdetector, which an analyst at the site's parent company told USA Today poured in across the country. Pins mark places named in news coverage: Chicago, which NBC Chicago said Downdetector listed among the hotspots, and Dallas / Irving, Texas, where CBS News reported a failed deposit at a Chase branch and the Associated Press photographed a Chase ATM showing it was not working. Based on user reports via Downdetector and news coverage, not official bank data. Sources: USA Today, BBC, NBC Chicago, CBS News, Associated Press. Base map: U.S. Census Bureau, 2023.

Updates

🔄 Update, 8:15 p.m. CT: A more specific cause, and Bank of America weighs in. Fox Business, citing an FBI official it did not name, reports that the disruption was traced to a software release JPMorgan Chase rolled out earlier Monday that affected a subset of its systems. The official said there was no indication of malicious or external cyber activity and that the impact was limited to JPMorgan Chase and to transactions at other banks where Chase was a party. That account comes from an anonymous official, not a public FBI statement, but it fits what Chase has said all day. Bank of America said on the record that its “systems have been operating normally today.” Fox Business also reports that Wells Fargo told it the bank was not affected by Monday’s events. That is hard to square with the “Online Banking is temporarily unavailable” notice Wells Fargo posted earlier, and the bank has not explained the difference. Chase has said transactions are posting normally, and Plaid has marked its Chase problem resolved.

✅ Update, 6:55 p.m. CT: Plaid marks the Chase problem resolved. Plaid, which connects bank accounts to outside apps, changed its status notice to “Resolved,” saying “the intermittent errors on Chase’s side have been resolved.” Together with Chase’s earlier statement that “transactions are now posting normally,” that is the second independent sign that the bank at the center of today’s disruption has recovered. Wells Fargo is still the open question. It has not announced that online banking is restored, and it declined to comment to Reuters. ABC News reported earlier that the bank’s “technical issues” notice was no longer on its site. We will close this tracker once Wells Fargo confirms service is back or the reports clearly fade.

✅ Update, 6:10 p.m. CT: Chase says transactions are back to normal. “Transactions are now posting normally,” a Chase spokesperson told NBC News around 6:30 p.m. ET (5:30 p.m. CT). That is the first restoration statement from the bank at the center of today’s disruption. NBC also reports, citing an unnamed person familiar with the situation, that regulators were in touch with the affected banks right away and “quickly determined this was contained.” That claim comes from an anonymous source, and no regulator has made a public statement. Wells Fargo has not yet said its online banking is fully restored, though Downdetector reports for it had fallen to almost 400 from a peak above 1,050, according to the BBC. Plaid’s notice about Chase connections still says “Investigating,” so some apps that link to Chase accounts may lag behind. Customers who were charged fees or saw failed payments today should keep records and ask their bank about reversals.

🔄 Update, 5:50 p.m. CT: The BBC’s live page now lists Downdetector figures showing reports well down from their peaks at all four of the most-reported banks: Chase is at more than 1,300, down from almost 5,000; Bank of America is at about 700, down from more than 2,100; U.S. Bank is at more than 450, down from more than 1,050; and Wells Fargo is at almost 400, down from more than 1,050. Those are user complaints, not confirmed outages, and they show the problem is easing but not over. PNC told Newsweek that the transaction delays it saw outside the bank “appear to be resolving.” Neither Chase nor Wells Fargo has announced that service is fully restored. Plaid still lists the Chase connection problem as “Investigating.”

🔄 Update, 5:30 p.m. CT: The decline in outage reports now extends beyond Chase. The BBC reports that as of 6 p.m. ET (5 p.m. CT), Chase, Bank of America and U.S. Bank had all seen a fall in the number of reported outages on Downdetector, and that problems “appeared to be easing for many customers by early Monday evening.” Downdetector counts user complaints, not confirmed outages, so this is a sign of recovery rather than an all-clear. Chase still has not announced that service is fully restored, and its stated target remains a fix by the end of the day. Wells Fargo has not issued a restoration statement. Plaid’s notice is unchanged and still lists the Chase connection problem as “Investigating,” and the Federal Reserve’s payment services still show no notifications.

🔄 Update, 5:15 p.m. CT: Plaid has downgraded its description of the Chase problem. Its status notice now says Plaid is “seeing intermittent errors for a small percentage of users due to issues on Chase’s side.” Earlier today the same notice said Chase was “experiencing downtime impacting all channels and data recipients.” Plaid edited the existing notice rather than posting a new timestamped update, and it still lists the incident as “Investigating” and a partial outage. That is a sign of recovery for apps that connect to Chase accounts, not an all-clear. Chase has not yet announced that service is restored, and its target remains a fix “by the end of the day today.” Wells Fargo has not issued a restoration statement either. The Federal Reserve’s payment services still showed no notifications.

🔄 Update, 4:45 p.m. CT: Reports are falling, but Chase has not given an all-clear. Tom’s Guide, which is tracking the outage live, said Downdetector reports for Chase roughly halved within an hour, from about 3,800 to about 1,780. It also relayed posts from some customers saying they could log in, use Zelle, and withdraw money again, while others still could not reach their accounts. Those are user reports, not a bank confirmation. Yahoo Finance also reported that complaints began declining Monday afternoon but stayed elevated at several banks. Chase’s most recent public word is still the target to resolve the issue “by the end of the day today,” and Tom’s Guide noted the bank did not say which time zone it meant. At this check, Plaid’s Chase notice still read “Investigating,” and the Federal Reserve’s payment services showed no notifications.

🔄 Update, 4:15 p.m. CT: More banks have said they were not affected. Truist, PNC, and Capital One each told the BBC they had not been impacted, despite customer reports naming them. That leaves Chase as the only bank confirming a fault of its own, and Wells Fargo as the only other bank that confirmed an online-banking outage. Chase posted its software-bug statement on its own X account, according to The Washington Post and Daily Voice. Daily Voice also noted that Chase did not say which other banks were affected, and that its statement does not establish that the bug caused every problem reported elsewhere. Still unresolved at this check: Chase’s goal remains a fix “by the end of the day today,” Plaid’s Chase notice still read “Investigating,” and the Federal Reserve’s payment services showed no notifications.

🔄 Update, 4:00 p.m. CT: Early signs of easing, but no all-clear. ABC News reports that Wells Fargo’s website no longer carries its earlier notice about “technical issues.” Wells Fargo has not issued a restoration statement, so we are not counting it as resolved yet. ABC also confirmed that all Federal Reserve-operated payment systems, including ACH transfers between banks, were operating normally. A Capital One spokesperson told CBS News the bank had not been affected and was operating normally. That puts Capital One’s spike in user reports in the same category as Truist’s: unconfirmed by the bank. WIRED attributed JPMorgan’s software-bug statement to spokesperson Pablo Rodriguez. Based on Downdetector user reports, WIRED said problems began around 9:30 a.m. Eastern and peaked around 2 p.m. Eastern. Chase itself has not announced a fix, and Plaid’s Chase notice still read “Investigating” at this check.

🔄 Update, 3:35 p.m. CT: JPMorgan names a cause. In a new statement quoted by NBC News (updated 4:17 p.m. Eastern), the bank said: “JPMorganChase has experienced a temporary issue related to a software bug in on-premise hardware systems.” It said the problem was not “cyber-related.” It also said the problem was not hitting the entire banking system: “Other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us.” Customers still have “access to their accounts and funds,” it said, adding: “We’re working diligently to resolve this by the end of the day today.” Separately, a Justice Department official with direct knowledge of the matter told MS NOW there was “no evidence of any attack.” The official spoke on condition of anonymity, so this is not a formal department statement. The New York Post reported that Downdetector complaints appeared to peak in the early afternoon. What is still open: Chase has given a target, not a confirmed fix. Plaid’s Chase notice still read “Investigating” at this check. Wells Fargo has not explained its own online-banking outage, and JPMorgan’s statement does not address it. The Federal Reserve’s payment services still showed no notifications.

🔄 Update, 3:00 p.m. CT: The Associated Press has updated its story under a new headline, “A technical issue at JPMorgan Chase triggers online banking delays across major US banks.” AP now reports that the Chase problem “caused ripple effects throughout the financial system.” That fits what Zelle and U.S. Bank said earlier: delays at other banks came from payments to or from Chase rather than separate failures. Wells Fargo’s online-banking outage has not been explained, and it has not been linked to Chase by any bank or named outlet. AP also reported that Chase said the problems were not the result of a cyberattack and that it was working to bring services back online. NBC News (updated 3:25 p.m. Eastern) put the potential reach in context: Chase has about 94 million U.S. customer relationships, 5,000 branches, and 15,000 ATMs. No restoration has been announced. As of this check, Plaid’s Chase notice still read “Investigating,” and the Federal Reserve’s payment services showed no notifications.

🔄 Update, 2:45 p.m. CT: Markets noticed. Fox Business reported at 3:06 p.m. Eastern that bank shares fell in afternoon trading as the outage reports spread: JPMorgan Chase was down more than 2.4%, Bank of America more than 2.1%, Wells Fargo about 2%, and Capital One about 1.2%. Fox Business noted the broader market was already trading lower before the outages. Forbes Middle East, citing Forbes, said Downdetector logged more than 5,000 Chase reports at the peak, with about 1,500 for Bank of America. Those are user-submitted reports, not confirmed outage figures. It also pointed out that Plaid posted an identical Chase disruption notice on October 20, which was later resolved. Nothing has changed on the fixes: as of this check, Chase had announced no restoration, Plaid’s Chase notice still read “Investigating,” the Federal Reserve’s payment services still showed no notifications, and no bank had named a cause beyond Chase’s “technical issue.”

🔄 Update, 2:30 p.m. CT: Chase’s problems reach beyond the app. NBC News, in a report updated at 3:16 p.m. Eastern, said the issues were affecting both online and in-person branch transactions, and that a person familiar with the matter said it was unclear how long a fix would take. A second source told NBC News the problem was an internal technical bug, not a cyber issue. CBS News quoted a Chase customer who said a Dallas branch could not complete his check deposit. That confirms through named outlets what earlier Reddit posts claimed about branches. Chase’s statement to Newsweek adds: “This is a technical issue, not cyber related.” Newsweek also reported that Citibank customers were not affected as of Monday afternoon and that Citi is monitoring the situation. As of this check, there was still no resolution: Plaid’s Chase notice was unchanged, Wells Fargo’s outage page still said online banking was unavailable, and the Federal Reserve’s status page showed no notifications for Fedwire, FedACH, or FedNow. We found no statement from federal regulators.

🔄 Update, 2:18 p.m. CT: The outages were still underway as of this check. Wells Fargo’s outage page still said online banking was temporarily unavailable, while ATMs, branches, and phone support remained available. Plaid still listed a service disruption affecting Chase connections, first posted at 9:11 a.m. Central, and said it would update the notice when Chase resolved the issue. The Federal Reserve’s service-status page still showed normal operations for Fedwire, FedACH, and FedNow, with no notifications. We found no statement from the FDIC, CISA, or the Treasury Department about today’s outages. Chase has not posted a resolution; its earlier statement, still cited in later coverage, described a technical issue, not a cyberattack, and said customers still had access to their funds. Bank of America declined to comment, according to NBC Chicago. U.S. Bank has said its systems are not directly impacted, though Zelle payments with other institutions may be delayed. Zelle told CBS News, in a report updated at 3:03 p.m. Eastern, that its service was “operating as it should,” while some delays can come from problems at participating banks; earlier, a Zelle spokesman told NBC News and NBC Chicago, “this is a Chase issue.” Capital One and Truist have not confirmed outages; reports for those banks remain user-generated, including on Downdetector, as described by CBS News, Newsweek, and Yahoo Finance. A follow-up X search for bank-outage chatter counted about 18,254 posts between 1 and 2 p.m. Central, and about 4,153 from 2:00 to 2:15 p.m. Posts tying the outages to the November 17 rumor remained a small share: 34 in the 1 p.m. hour, and 10 from 2:00 to 2:15 p.m.

🔄 November 16, 2026, afternoon CT: First published. As of about 1:35 p.m. Central, Wells Fargo’s site still said online banking was temporarily unavailable, Plaid still listed a partial outage affecting Chase connections, and the Federal Reserve’s service-status page still showed no notifications. Chase, Wells Fargo and Plaid had not posted a resolution notice in the coverage and status pages we rechecked after 1:20 p.m. Central. We will update this page if the banks, Plaid, or a U.S. banking regulator issue a new official statement.

Large U.S. banks had a rough Monday on the internet. Customers reported trouble logging into apps and websites, moving money, and seeing balances. Some posts on X treated the disruption as proof that a rumor about November 17 — the day, in that story, when banks are compromised and the internet is shut down — had arrived a day early. The outages are real. The leap to that rumor is not supported by the official record so far. Here is what can actually be checked, with times in Central Time.

What’s being said

User reports on Downdetector and on social media spiked around midday for several large banks and for the payment app Zelle. News outlets including CBS News, Newsweek, NBC Chicago and Reuters described a cluster of complaints involving Chase, Bank of America, Wells Fargo, U.S. Bank, Capital One, Truist and Zelle. Chase, Wells Fargo, Bank of America, Downdetector and Zelle were among U.S. trends on X during the noon hour. An X search for bank-outage chatter counted about 274 posts between 11 a.m. and noon Central, about 5,563 between noon and 1 p.m., and about 3,101 from 1:00 to 1:18 p.m. About 30 posts an hour in that window tied the outages to the November 17 rumor.

Some customer posts went further than “the app is down.” People described delayed transfers, trouble cashing checks, and, in unverified Reddit posts relayed by Tom’s Guide, Chase branch staff saying their systems were down. Those branch claims have not been confirmed by the bank. A smaller stream of posts framed today’s problems as the opening act of the November 17 story. That rumor, which we examined separately, claims that a “dark web” warning says major banks will be compromised, balances wiped to zero, and the global internet locked down for three months. Today’s confirmed facts do not match that script.

What’s confirmed

Chase has confirmed a technical problem and has said it is not a cyber issue. A spokesperson told CBS News and other outlets: “Due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds. We are working to resolve this as quickly as possible.” CBS reported that the bank described the problem as a technical bug, not a cyber issue. Chase Support also told a customer on X that the bank was “working to resolve an issue with online banking,” as quoted by NBC Chicago. Some customers saw a message in the Chase app saying, “Some services aren’t available. We’re working on them. Please try back later.”

Wells Fargo has also confirmed a problem, in a message still on its site as of about 1:35 p.m. Central: “Online Banking is temporarily unavailable.” The same page says customers can still reach their accounts through ATMs, banking locations and customer service, and that phone bankers remain available around the clock.

Plaid, the company many apps use to connect to bank accounts, still listed a partial outage affecting Chase connections as of about 1:35 p.m. Central. The incident was first posted at 10:11 a.m. Eastern (9:11 a.m. Central). Plaid said Chase downtime was affecting “all channels and data recipients,” including new item connections and API calls through Plaid, and that it would update the page when Chase resolved the issue.

Downdetector counts, which measure user reports rather than official bank telemetry, were still climbing into early afternoon. NBC Chicago reported more than 4,000 Chase reports as of 12:19 p.m. Central. Newsweek, in an update issued at 1:24 p.m. Central, cited more than 4,400 Chase reports as of 12:52 p.m. Central, more than 1,300 for Bank of America, more than 640 for Wells Fargo shortly before 1 p.m. Central, and more than 600 for U.S. Bank, with reports still climbing as of 1 p.m. Central. CBS News, in an update issued at 1:30 p.m. Central, said nearly 4,800 users had reported problems with Chase as of 1 p.m. Central, the most of any bank in that tally.

The Federal Reserve’s service-status page showed no notifications as of about 1:35 p.m. Central. Fedwire Funds, FedACH and FedNow are among the services listed on that page, which was displaying a normal-operations status. Reuters, in a 1:12 p.m. Central dispatch, reported that CNBC, citing a source, said there was no indication “bad actors” were involved in JPMorgan’s technical issue and no sign that a bug was affecting multiple banks at the same time.

What’s unconfirmed

Spikes in user reports are not the same thing as a confirmed outage. Bank of America, U.S. Bank, Capital One, Truist and Zelle all appeared in Downdetector or news tallies on Monday. As of early afternoon Central, those firms had not issued the same kind of public confirmation that Chase and Wells Fargo had. NBC Chicago reported that Bank of America declined to comment, and that Zelle told the station “this is a Chase issue.” Tom’s Guide, in a live update around 12:56 p.m. Central, said it was seeing hundreds of reports for Bank of America, Wells Fargo and Zelle, but believed the incident was isolated to Chase, with knock-on trouble for people trying to send money to or from a Chase account. That remains an assessment, not a finding from the other banks.

No official resolution had been posted by Chase, Wells Fargo or Plaid in the status pages and coverage we rechecked after 1:20 p.m. Central. We also found no statement from CISA, the Federal Reserve or the FDIC describing a system-wide banking failure, a coordinated cyberattack, or wiped balances.

Why this is not the November 17 rumor

The November 17 rumor claims that major banks will be compromised and balances wiped to zero, and that the global internet will then be locked down for three months. We tracked that claim in a separate chatter check. Today’s record is different on every important point. The internet itself is not down. Chase says customers still have access to their accounts and funds, and that the cause is a technical issue, not a cyberattack. Wells Fargo says ATMs, branches and phone support still work. The Federal Reserve’s listed payment services had no status notifications at this writing. The rumor itself was not among the U.S. trends; only a thin slice of the outage chatter, about 30 posts an hour in the early-afternoon window we measured, tried to connect the two.

A real outage can still be costly and frustrating. It is not evidence that the anonymous “dark web” warning is coming true. The only official nationwide event still on the calendar for November 17 is the already announced, one-minute Emergency Alert System test on radio and television, not a bank or internet shutdown.

Our view: Take the confirmed bank statements at face value and keep ordinary access routes in mind — ATMs, branches and phone banking where those are open — until the apps are working again. Do not treat Monday’s outages as proof of the November 17 shutdown story, and do not make sudden financial moves on the strength of social-media claims that balances are about to be wiped.

Label key

  • ✅ Confirmed An official record, or two or more independent outlets, agree.
  • ❓ Unconfirmed Reported or claimed, but not yet independently verified.
  • ⚠️ Disputed Contradicted by the evidence or by credible sources, or actively contested.
  • Scales icon Factual Straight reporting that holds up across outlets on different sides.
  • Donkey icon Leans Left The facts hold, but the coverage tilts left: one-sided, loaded language, missing context or a single anonymous source.
  • Elephant icon Leans Right The facts hold, but the coverage tilts right: one-sided, loaded language, missing context or a single anonymous source.
  • Megaphone with hammer and sickle icon Likely Propaganda State-run or state-aligned media, a militant press office, a partisan campaign or group, or unverifiable spin.

Each story gets one confidence tag and one source-lean label, plus a one-line Lean note explaining the call. Every side is held to the same standard. More on how we cover the news.

Sources