Notice of Suspension for TRON (TRX) Network Deposit and Withdrawal (Nov 10, 2026)
- Published
- Updated
Bybit said it will suspend TRON (TRX) network deposits and withdrawals on Nov. 10, 2026. Kraken said at 18:14 UTC and again at 18:15 UTC on Nov. 10 that it was investigating delays affecting deposits and withdrawals across multiple blockchain networks.
Key claims & sources
What it means
TRON is one of the major networks used for moving tokens on chain, and Bybit’s notice puts that rail into a temporary hold for deposits and withdrawals on Nov. 10, 2026. Kraken’s notices on the same day show that exchange transfer operations can be disrupted across more than one blockchain network at the same time. For users, that means on-chain movement through these venues may be unavailable or slower than usual until the exchanges restore normal processing.
Exchange transfer availability sits at the center of crypto custody and trading because users rely on it to move assets between wallets and platforms. When a venue pauses a network such as TRON or reports delays across multiple chains, traders and builders have to adjust around the exchange’s operational controls rather than the blockchain itself. That tension runs against the expectation that crypto rails stay open continuously, even when individual service providers interrupt access. (per kraken.com)
Bybit’s TRON suspension and Kraken’s multiple-network delay notices point to a common operational problem: centralized platforms can limit access to blockchain transfers without changing the underlying networks. The immediate effect is on deposits and withdrawals, not on the broader existence of TRON or the chains Kraken supports. Readers still do not know how widely Kraken’s issue reached, which networks were affected, or when normal processing will return. (per kraken.com)
Market reaction i
TRON rose 0.1% in the 4 hours after the first headline, after a flat 2 hours before.
48 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| today | Initia · Private key leak incident | $615k |
| 2 days ago | Swarm · Supply chain attack incident | no figure in dollars |
| 2 days ago | Ankr Bridge · Cross-Chain Message Spoofing incident | $304.5k |
| 3 days ago | ACryptoS · Missing Input Validation incident | $665.4k |
| 3 days ago | LNbits · Software vulnerability incident | $1.7k |
4296 incidents stored