New: Upbit Caution & Delisting Alerts

May 3, 2026

Last updated 2026-07-18

Your Upbit feed now carries two trade-actionable risk events alongside listings: caution_released (caution designation lifted, often a positive technical signal) and spot_delisting (final removal from spot). Both travel over the same WebSocket connection as listings, with the same end-to-end delivery from our Korean endpoint.

What we broadcast

Two Upbit-specific event types, both also emitted by Bithumb when its parser sees the equivalent Korean phrasing:

"caution_released"     // 거래 유의 종목 지정 해제 — caution lifted (often a technical bounce)
"spot_delisting"       // 거래지원 종료 — final removal from spot

caution_released is our event name for the moment Upbit lifts a caution designation already placed on a token (거래 유의 종목 지정 해제) — the token had previously been flagged for review (concerns around liquidity, regulatory status, persistent volatility, supply schedule, etc.) and is now returning to normal trading status. spot_delisting is the inverse outcome: final removal from the spot market (거래지원 종료).

See the message reference for the full schema and example payloads.

The Upbit caution lifecycle, end to end

An Upbit risk event rarely arrives out of nowhere. A token usually enters the pipeline when Upbit attaches a caution designation (거래 유의 종목 지정) — a formal flag that the asset is under review for concerns such as thin liquidity, an opaque supply schedule, governance or team-disclosure gaps, regulatory uncertainty, or persistent abnormal volatility. That designation opens a review window during which the token keeps trading but sits under a cloud. The window resolves one of two ways, and those two outcomes are exactly the events your feed carries: the caution is lifted (caution_released) and the token returns to normal status, or the review ends in final removal (spot_delisting). We forward the two decision points because they are the moments the market actually re-prices — the initial flag is informational, the resolution is trade-actionable.

Because both endpoints share one lifecycle, they are useful to read together. A token that was flagged weeks ago and then earns a caution release is a different setup from a fresh listing pump: the overhang of forced or fearful selling clears, and short covering plus returning KRW-market flow can drive a sharp mean-reversion. A delisting, by contrast, is a hard deadline — Upbit publishes the exact date and time trading support ends, and liquidity thins into that cutoff.

Reading a caution cascade

Upbit does not review tokens strictly one at a time. It periodically publishes batches of caution designations, and those batches often foreshadow a cluster of resolutions weeks later — several releases, several delistings, sometimes both inside a single composite notice. We split composite titles into separate events with distinct listingType values so a batch never collapses into an ambiguous message. Watching the cadence of designations gives you a rough leading indicator of when the next wave of trade-actionable resolutions is likely to land, and monitoring Bithumb's matching event class in parallel widens that picture across both major Korean venues.

The tokens themselves are public: Upbit posts every designation, release, and delisting to its official notice board, and the underlying investor-protection rules trace back to the framework overseen by South Korea's Financial Services Commission. What your feed adds is that the Korean-language notice is parsed, the ticker is normalized, and the event is typed and delivered in real time — so your system reacts the instant the decision publishes rather than while you are still reading it.

Trading implications

Both events have a clear historical price-reaction direction: spot_delisting is bearish (final removal from the spot market) and caution_released is bullish (caution status lifted, the overhang of forced selling clears). On Upbit specifically, the Kimchi premium dynamic amplifies both directions — a delisting often triggers a sharper drop than the same event on Binance because Korean retail flow concentrates here, and a release can produce a quick mean-reversion as that flow returns.

Execution differs by direction. On a spot_delisting, the actionable read is usually risk-off: reduce or exit exposure well before Upbit's stated support-end timestamp, since KRW-side liquidity dries up as the deadline approaches and the final hours can gap. On a caution_released, the move is typically front-loaded into the first minutes as the designation overhang lifts — the same speed premium that governs listings applies here, because the edge decays as the release propagates from the Korean notice board to global order books.

Disclaimer. CryptoListing.ws is a real-time data feed, not a financial advisor. The directions above are observations of historical behaviour — not guarantees, predictions, or recommendations. Markets are noisy, signals fail, and past behaviour does not determine future outcomes. You are solely responsible for any trading decisions you make on the basis of these events.

Detection & API

Both event types are delivered over the same WebSocket connection as listings, delistings, and airdrops. A typical caution_released message looks like:

{
  "type": "announcement",
  "title": "신세틱스(SNX) 거래 유의 종목 지정 해제 안내",
  "ticker": "SNX",
  "publisher": "upbit",
  "listingType": "caution_released",
  "detectedTimestampUs": 1746280800834000,
  "dispatchTimestampUs": 1746280800842117,
  "abnormalDetectionLatency": false
}

And a spot_delisting message:

{
  "type": "announcement",
  "title": "룸네트워크(LOOM) 거래지원 종료 안내 (5/7 15:00)",
  "ticker": "LOOM",
  "publisher": "upbit",
  "listingType": "spot_delisting",
  "detectedTimestampUs": 1746280800834000,
  "dispatchTimestampUs": 1746280800842117,
  "abnormalDetectionLatency": false
}

One detail worth knowing: a single Upbit announcement occasionally pairs a release with a delisting, and Upbit also publishes multi-ticker delistings using comma-separated lists inside parentheses (e.g. "이더리움클래식(ETC), 웨이브(WAVES), 머큐리(MER) 거래지원 종료"). Multi-ticker events keep the listings convention: one message with the tickers joined comma-separated in the ticker field. Composite titles that span both stages are split into separate WebSocket events with distinct listingType values, so your bot can route each side independently — no parsing logic on your end.

Filtering is a one-liner — exactly the same code path you use for Bithumb, just routed by publisher:

def on_message(ws, msg):
    data = json.loads(msg)
    lt = data["listingType"]
    cex = data["publisher"]

    if lt == "caution_released":
        clear_risk(cex, data["ticker"])
    elif lt == "spot_delisting":
        unwind(cex, data["ticker"])

Get started

Both event types are included in every plan, the free SpeedTrial key and FreeDelayed (full feed, +240 ms) included. Grab an API key on Telegram via @CLWfeed, then check the pricing page and developer docs to get connected. Upbit events are dispatched from our Tokyo endpoint wss://cryptolisting.ws; filter with ?cex=upbit to scope your subscription, or ?cex=bithumb,upbit to capture both Korean exchanges on a single stream and route by the publisher field.

This article is for informational purposes only and is not financial advice. CryptoListing.ws is a technical data feed service — see Legal.

Related

• New: Bithumb Caution & Delisting Alerts — the same caution-release / delisting events on the second-largest Korean venue.
• Bithumb vs Upbit: Listing Strategy — comparing the two major Korean exchanges for listing alpha.
• Upbit Listing Alerts — full coverage page with Korean-market context and FAQs.