Banks froze today. The internet "shutdown" is a test.
Four big US banks had problems at once. The three-month blackout rumor was false. Bitcoin kept settling.
- Chase outage reports
- 4,300+
- rumor claims, all false
- 3
- Bitcoin blocks, noon to 3 p.m. ET
- 26
- Bitcoin transactions settled
- 135,656
Today Chase customers watched transfers hang. Tomorrow the internet "shuts down for three months."
Only one of those is real.
On Monday @Chase, @BankofAmerica, @WellsFargo and @usbank customers all hit problems at once. Chase alone passed 4,300 reports on Downdetector. Chase called it a technical issue, "not cyber related," and said customers still have access to their funds.
Tomorrow's "blackout" started as one X post in Portuguese citing an unnamed dark web source. It promised hackers zeroing out banks, the internet off for three months, and a "super-powerful AI" patching everything. Telegram channels pushed it. A spliced Simpsons clip did the rest.
What actually happens on Nov 17 at 2:20 p.m. ET is a @fema and @FCC test, per FCC public notice DA 26-989. It covers the Emergency Alert System on TV and radio, for about a minute. Not the internet, not your bank.
The same day, Fed governor Michael Barr said in a speech that AI models have already exploited the same weak spot human hackers use, when many firms lean on one shared platform provider. That risk is real. Today wasn't it.
Between noon and 3 p.m. ET, while bank apps were failing, Bitcoin added 26 blocks and confirmed 135,656 transactions (mempool data). No support line, no "try again later."
If your bank app froze tomorrow, where would you want your money to be?
Claim by claim
On Monday, Nov 16, 2026, customers of several large US banks reported problems at the same time. The same week, a rumor said the internet would go dark worldwide on Nov 17. We checked both.
-
01
REAL
Chase, Bank of America, Wells Fargo and U.S. Bank customers reported problems on Nov 16
Downdetector counts as reported by Gizmodo (updated 3:14 p.m. ET)
-
02
REAL
Chase passed 4,300 Downdetector reports
Same article: over 4,300 as of 1:27 p.m. ET. Bank of America passed 1,000. Wells Fargo, U.S. Bank and Zelle had hundreds each
-
03
REAL
Chase called it a technical issue, "not cyber related", and said customers can still reach their funds
Chase statement quoted by Gizmodo and others: "Due to a technical issue, some transactions are taking longer than usual to complete, but customers still have access to their accounts and funds."
-
04
FALSE
Hackers will zero out bank accounts on Nov 17
The rumor started as one X post in Portuguese citing an unnamed dark web source. Its author said it was unconfirmed. No group, no technical detail, no evidence
-
05
FALSE
The internet goes off for three months
Same source. Nothing official supports it
-
06
FALSE
A "super-powerful AI" will patch everything in the meantime
Same source. Unexplained claim
-
07
REAL
What actually happens on Nov 17 is a nationwide Emergency Alert System test at 2:20 p.m. ET
FCC public notice DA 26-989, released Sept 16, 2026. Backup date Dec 3
-
08
REAL
The test runs on TV and radio, for about a minute, and does not involve the internet
Same notice lists EAS participants: radio, TV, cable, satellite, wireline video. FEMA describes about one minute, "This is only a test"
-
09
REAL
Fed governor Michael Barr said AI models have exploited the same weak spot human attackers use, many firms relying on one shared platform provider
Speech, Nov 16, 2026, Milan, section "AI and Cyber Risk"
-
10
NOT CLAIMED
That risk caused this outage
We did not link the two. Chase says the outage was not cyber related
-
11
REAL
Between noon and 3 p.m. ET, Bitcoin added 26 blocks and confirmed 135,656 transactions
mempool.space, blocks 976155 to 976180. Reproduce below
Reproduce claim 11
python3 scripts/btc_blocks_window.py 2026-11-16T17:00:00Z 2026-11-16T20:00:00ZOutput ends with 26 blocks (976155 to 976180), 135,656 transactions. 17:00 to 20:00 UTC is noon to 3 p.m. Eastern. Block timestamps are set by miners and can be off by a few minutes.
Corrections
None so far. If you find an error, open an issue with the source.