Crypto Delisting Alerts — Binance, Upbit & Bithumb

Delistings move price as sharply as listings do — usually the other way. When an exchange announces that a pair is being removed, or flags a coin for review, holders head for the exit and the discount opens fast. CryptoListing.ws streams delisting and caution announcements from Binance, Upbit and Bithumb over a single real-time WebSocket, as structured JSON, the moment they are published.

Why delisting alerts matter

A delisting announcement is a scheduled negative catalyst. The exchange names an effective date, deposits and withdrawals wind down, and trading of the pair stops for good. Between the announcement and the effective date, the market re-prices the token — often within seconds of the notice going live. For anyone running an automated strategy, being early to the announcement is the entire edge: whether you are exiting a position, hedging on a venue that still lists the token, or trading the reaction, the announcement is the trigger and every moment after it is decay.

The same is true one step earlier in the lifecycle. Before a full removal, exchanges publish warnings: Binance adds a Monitoring Tag, and the Korean exchanges apply a caution designation. These are not delistings, but they are strong, market-moving signals that a delisting may be coming — and they are announced on the same channels.

Three delisting vocabularies, one feed

Each exchange describes removals and warnings in its own terms. The feed normalizes them into a small set of machine-readable listingType values so one handler covers all three exchanges.

A quick vocabulary map, because the words are easy to conflate:

• Delisting — the pair is permanently removed. Terminal, and always negative for the pair being removed.
• Monitoring Tag (Binance) — a visible warning label on a coin that keeps trading. It flags elevated risk; it can be added and later removed without a delisting ever following.
• Caution / investment warning (Upbit 유의종목, Bithumb) — the Korean-exchange equivalent of a review flag. It can escalate to a delisting or be lifted. The lift is itself a tradable event (caution_released).

REST polling vs real-time push

Most delisting trackers you will find are polling tools. They query an exchange's REST announcement endpoint on a fixed schedule — commonly anywhere from every 30 minutes down to roughly 60 seconds for the fastest ones — and surface anything new since the last check. That is fine for a dashboard, but on a scheduled negative catalyst the poll interval is your worst-case delay: an announcement that lands one second after a poll waits out the rest of the interval before anyone sees it.

CryptoListing.ws works the other way around. Instead of you pulling on a timer, the service pushes the announcement to every connected client over WebSocket the instant it is published — no poll cadence to wait out. The result is millisecond-class delivery of a structured event rather than a periodic snapshot of a web page. You measure the network leg yourself using the timestamps in each message.

Message shape

Every delisting or caution event is a single JSON object. Treat ticker as potentially comma-separated: one notice can cover several coins at once.

{
  "type": "announcement",
  "title": "Binance Will Delist TOKEN on 2026-08-01",
  "ticker": "TOKEN",
  "publisher": "binance",
  "listingType": "spot_delisting",
  "detectedTimestampUs": 1710345000005000,
  "dispatchTimestampUs": 1710345000006000
}

Connect and filter to delistings

Authenticate with an X-API-Key header on the WebSocket upgrade. Use the Tokyo endpoint for the full multi-exchange feed, or the Seoul endpoint for Upbit-only. Then keep only the delisting and caution event types you care about.

# pip install "websockets>=14"  — the header param is additional_headers
# (extra_headers was removed in websockets v14+)
import asyncio, json, websockets

API_KEY = "dsk_your_key_here"
WS_URL  = "wss://cryptolisting.ws"  # Tokyo, all exchanges

DELISTING_TYPES = {"spot_delisting", "futures_delisting",
                   "monitoring_tag_extend", "caution_released"}

async def run():
    headers = {"X-API-Key": API_KEY}
    async with websockets.connect(WS_URL, additional_headers=headers) as ws:
        async for raw in ws:
            msg = json.loads(raw)
            if msg.get("type") != "announcement":
                continue
            if msg["listingType"] in DELISTING_TYPES:
                for ticker in msg["ticker"].split(","):
                    print(msg["publisher"], msg["listingType"], ticker)

asyncio.run(run())

Per-exchange delisting pages

This is the pillar overview. Each exchange has its own patterns, wording and pace of removals — dive into the dedicated pages:

• Binance delisting alerts — spot and futures delistings plus Monitoring Tag changes.
• Upbit delisting alerts — 유의종목 investment warnings and 상장폐지 removals.
• Bithumb delisting alerts — caution designations and delistings on the KRW market.

FAQ

What is a crypto delisting alert?

A structured JSON event, pushed over WebSocket the moment an exchange publishes a removal or caution notice. It carries the ticker, publisher, listingType and microsecond-precision timestamps so an automated system can react immediately.

Which exchanges are covered?

Binance, Upbit and Bithumb. See the full announcement API reference for every event type and both endpoints.

Does a Monitoring Tag or caution mean a delisting is certain?

No. Both are warnings on a coin that is still trading. They frequently precede a delisting but do not guarantee one; a distinct spot_delisting event marks the actual removal.

Can I get an audit trail of past delistings?

Yes — recent detections, including delistings and caution changes, are listed on latest detections.