463 of 5,110 Coin–Network Pairs Are Closed for Withdrawal Right Now: How to Check Yours

Bottom line first: an exchange's withdrawal menu often still lists a coin–network pair that its own public API has flagged withdrawable = false. Our data engine counts these every day. Snapshot 2026-10-14T14:06:01Z (Bitget's public coin API): 463 of 5,110 pairs are currently closed for withdrawal — including BTC on Lightning and USDT on Aptos. This is not a bug story; it is the normal operating state of any large multi-chain exchange, and you should plan around it before you move money, not after.

1. What the numbers say (one exchange, fully measured)

From the same API snapshot:

• 5,110 coin–network pairs tracked, of which 463 show withdrawal-disabled at snapshot time.
• Pairs you would assume are always open, currently are not: BTC / Lightning, USDT / Aptos, ETH / Blast, ETH / Robinhood chain, TUSD / TRC20, TUSD / Avalanche C-Chain, AXS / BEP20 and / Ronin.
• Some small-cap coins are closed on every network we track (e.g. OATH, TOWER, BWB — closed on all 4 of their listed pairs each).
• The same API's congestion field reads normal on all 5,110 rows today — which tells you something too: as shipped, that field currently discriminates nothing, so we don't use it as a signal. We report it as-is rather than dressing it up.

Coverage honesty: this is one exchange, because only its public coin endpoint gives us the whole matrix. The other four exchanges we list on this site do not expose an equivalent endpoint we have collected — so "which pairs are closed on Binance/OKX/Bybit/Gate" is not measured here, and no cross-exchange ranking of suspension counts should be inferred from this page.

2. Why exchanges close a pair — and what our data does not claim

We observe which pairs flip and when; we do not have a verified, per-incident cause for each flip. Common publicly stated reasons (from exchanges' own announcements, which we link in tickets but do not reproduce here) include chain maintenance and node upgrades, deposit/withdrawal contract migrations, security reviews, and low-liquidity delistings. Treat any specific "why" for a specific flip as unknown unless you can see the exchange's own dated notice — including ours: our change feed records the flip, not the reason.

What we can show: this is a moving baseline. Between 2026-10-12T19:00Z and 2026-10-14T12:08Z our engine logged 4,713 withdrawal-rule changes (fees, minimums, flags) on this one exchange's API alone. That is why every number on this site carries a snapshot date.

3. What to do with this, practically

1. Check before funding or withdrawing, not after: the deposit-path engine answers "can I move X out of exchange Y on chain Z today" from the live rules table.
2. If your intended pair is closed: do not deposit on that chain "and wait" — a closed withdrawal flag on the chain you deposited with can leave funds parked until the pair reopens. Pick an open pair instead; that's a route decision, not a risk decision.
3. If your withdrawal was requested before a pair closed and is stuck: that is a ticket conversation — use the pre-transfer check and contact the exchange with the transaction details.
4. If you hold a coin closed on every tracked pair: read the exchange's delisting/announcement page directly (linked in our tool results) — repeated full closure is usually a signal worth reading about before you act.

4. Our limits, plainly

• One exchange's matrix (Bitget, via its public API); the other four are not collected, so this page cannot tell you "which exchange suspends most often." We won't guess.
• The suspension flag is a moment-in-time API field; it changes without notice. Re-run the tool for the live value.
• We don't contact exchanges to restore your withdrawal — rescue work means preparing your ticket properly, and we publish the resolution statistics including failures.

Next steps

• Live check for your coin and network: deposit-path engine
• Why "pending" is often not the same problem: What a pending withdrawal is actually waiting for
• The four fatal pre-transfer mistakes (wrong chain is #1): Four things to check before any transfer

---

Data source and fetch time: all counts and flags are from Bitget's public API (/api/v2/spot/public/coins, fetched 2026-10-14T14:06:01Z; endpoint reachability re-verified live this day, 5,505 coins returned). The 4,713-change figure is from cexah's own daily change-detection feed over 2026-10-12T19:00Z–2026-10-14T12:08Z: https://www.cexah.com/track/summary?days=7 — the feed logs field flips, not exchange-stated reasons. Common closure reasons are described without citing a specific incident because we keep per-incident causes only when the exchange's own dated notice is in hand.

Disclaimer: This site provides education and tools, is not investment advice, and we do not guarantee any exchange's availability at any time — always re-check the live tool before moving funds.