We analyzed this claim: is it true that
security-related outages at Chainalysis disrupted the identification, screening or freezing of cryptocurrency stolen from Binance?

Two fresh outages hit Chainalysis screening tools on November 11 and 12, lasting nearly four hours and 53 minutes. However, no customer or transaction records prove that stolen Binance funds escaped detection or freezing during those windows, and a November 12 U.S. Justice Department update confirmed that asset freezes continued without measuring any impact from the outages.
RafaVisual artistComing December 1
JolinaMarketingComing December 1
Tracking Tools Falter Again as U.S. Seizes Binance Crypto
New outages hit the software used to trace stolen cryptocurrency, even as U.S. prosecutors secured court orders over more than $1.2 billion.
In a nutshell
Following the October 29 theft of roughly $6.3 billion in cryptocurrency from Binance, the tracking company Chainalysis suffered new service interruptions on November 11 and 12 while recovering from an unrelated security breach. At the same time, the U.S. Department of Justice announced that authorities and private partners had frozen more than $2.7 billion of the stolen funds, including over $1.2 billion backed by court orders. Both facts are confirmed, but without private exchange transaction logs, it remains unknown whether the tracking outages let any stolen funds slip past compliance checks.
Highlights
- Hackers stole approximately $6.3 billion in cryptocurrency from Binance on October 29, 2026, prompting global efforts to freeze the funds.
- Chainalysis's KYT transaction-monitoring service suffered an outage of roughly three hours and 55 minutes on November 11.
- A second Chainalysis disruption hit KYT, Address Screening, Sentinel and Reactor for about 53 minutes on November 12.
- The U.S. Department of Justice announced on November 12 that more than $2.7 billion in stolen Binance funds had been frozen, including over $1.2 billion under court seizure or restraint orders.
- No public transaction or customer records prove that stolen Binance transfers escaped detection or freezing during the Chainalysis outages.
From the Editor’s Diary
When digital thieves steal billions in minutes, stopping the money depends not only on police and courts, but on the uptime of private software tools that watch blockchain transactions around the clock. Even a brief outage raises hard questions about accountability when the logs needed to measure its impact stay behind closed doors.
Who's involved
Chainalysis
U.S. company whose software tracks cryptocurrency transactions, screens digital wallets and helps businesses and police trace stolen funds
goal → Bring its tools back online safely, protect customer data and prove its compliance software remains reliable
U.S. Department of Justice
Federal agency that prosecutes crimes and asks courts for legal authority to freeze or seize stolen assets
goal → Keep stolen Binance funds away from the thieves and secure legal control over recoverable money
TraderTraitor
Hacking group linked by U.S. officials to North Korea and accused of stealing billions of dollars in cryptocurrency from Binance
goal → Keep control of the stolen funds and move them before exchanges or courts can freeze them
Binance
Global cryptocurrency exchange whose online wallets were drained in the October 29 theft
goal → Recover the stolen money, protect users and assist investigators tracking the funds
Federal Bureau of Investigation
U.S. federal police agency coordinating cryptocurrency tracing and recovery with partner agencies
goal → Identify the hackers, alert exchanges to suspicious digital wallets and help block stolen funds
Chainalysis customers
Cryptocurrency exchanges, financial firms and investigators that rely on Chainalysis software to check transaction risk
goal → Keep transaction monitoring running smoothly and avoid processing tainted transfers without proper checks
In short
The software tools used by exchanges and police to spot stolen cryptocurrency suffered fresh outages in mid-November, raising questions about whether thieves could move looted funds while warning systems were offline. The tools belong to Chainalysis, a U.S. company whose tracking software helps cryptocurrency exchanges flag suspicious digital wallets and follow stolen money, which had been recovering from an unrelated security breach after hackers took about $6.3 billion from the global exchange Binance on October 29, 2026.
Next, investigators and exchanges must rely on private customer transaction logs to learn whether any stolen funds slipped past compliance checks while the software was down.
It is too early to tell whether those interruptions helped the thieves move money, because public status pages show when tools went offline, while proving a missed alert requires private exchange logs and exact transfer timestamps.
Previously in this story

Chainalysis Outage Leaves Stolen Crypto Impact Unproven
13 November 2026A security breakdown at crypto's top tracking firm disrupted transaction screening, but whether stolen Binance funds escaped remains unknown.Chainalysis faces claims cyberattack exposed customer access tokens
6 November 2026Fresh social media reports claim an intrusion at the cryptocurrency tracking firm hit live session keys and passwords, but independent verification remains absent.Chainalysis data breach exposes client contact lists
4 November 2026Intruders stole names and emails from the crypto-tracing firm, raising fresh risks of targeted scams.
How it unfolded
A Record Crypto Theft Tests Tracking Software
Unauthorized transfers began draining internet-connected wallets at Binance on October 29 at around 20:05 UTC. Early the next day, Binance confirmed losses of roughly $6.3 billion and said efforts were underway to freeze the stolen assets. Around the same time, Chainalysis disclosed an unrelated breach of its own systems that forced several tracking tools offline, leaving exchanges and investigators to ask whether they could still spot tainted Binance transfers while key monitoring software was unavailable.
Fresh Outages Hit Tracking Tools as U.S. Secures Seizure Orders
The software recovery that seemed underway after November 8 proved uneven, leaving open whether screening gaps slowed asset freezes. Specialist outlet CryptoSlate reported on November 9 that Chainalysis had restored its main investigation and screening tools, though its Investigations API (a direct software link used by automated systems) and Rapid Lookup remained under maintenance, and warned that status labels did not guarantee full access for every customer. Chainalysis restored its Data Solutions service on November 10 while continuing to reconnect customers, only for fresh failures to hit its KYT monitoring tool for nearly four hours on November 11 and disrupt KYT, Address Screening, Sentinel and Reactor for 53 minutes on November 12, even as some secondary tools stayed offline.
On November 12, the U.S. Department of Justice announced that government and private efforts had frozen more than $2.7 billion of the stolen Binance funds, including more than $1.2 billion under court-authorized seizure or restraint orders. While that update showed asset freezes moving ahead, it did not say whether Chainalysis interruptions caused any missed alerts or let thieves launder more money.
Where things stand
As of November 13, Chainalysis's public status page lists Reactor, KYT UI, KYT API, Address Screening, Sentinel and Data Solutions as operational, while Investigations API, Rapid Lookup, Rapid and Academy remain under maintenance or unavailable. No new outages were listed on November 13 at the time checked, though public status labels alone do not confirm continuous compliance checks for every customer.
The November 12 Justice Department announcement confirms court authority to seize or restrain more than $1.2 billion within a frozen pool exceeding $2.7 billion, though it does not show that all $1.2 billion is yet in government custody or reconcile the figure with Binance's earlier $2.85 billion frozen-or-intercepted estimate. Settling whether the outages caused missed freezes will require private customer transaction logs, alert timestamps and transfer records that have not been made public.
