Live data · By CoinNudge Research · Method reviewed 2026-09-08 · Guide updated 2026-09-12 · Live sources · Data observed at · Calculation okx-liquidation-pressure-1.0 · Auto-refresh about every 15 seconds
OKX crypto liquidations today: long vs short pressure
Current answer: As of , using OKX Public WebSocket: Rows rank the largest observed 15-minute OKX liquidation totals, not the assets most likely to reverse. CoinNudge observed $66,979.04 across 84 events. Liquidated longs are the larger observed side. This venue-specific cluster does not establish a market top or bottom.
Live sources
Explore data products · Check Market Events sample · Explore Telegram alerts
Current source-backed snapshot
This page ranks the 20 largest asset-level liquidation totals actually observed on the OKX public perpetual stream during the latest rolling 15 minutes. Ranking is by observed USD notional, not price change, market capitalization or predicted reversal. Each row separates liquidated longs from shorts, reports event count and side concentration, and shows whether available price, open-interest and spot-flow checks support a Telegram alert. These are OKX events rather than estimated whole-market liquidations, and a high rank does not prove a bottom, top or profitable entry.
Input documentation: OKX liquidation-orders WebSocket · CoinNudge liquidation methodology
Observation window: Rolling 15-minute observed OKX liquidation events
Calculation cadence: Auto-refresh about every 15 seconds
Calculation version: okx-liquidation-pressure-1.0
Download current dataset: JSON · CSV Raw values retain the dataset's published precision. Free fair-use limit: 60 requests per minute per IP, shared across all Research JSON and CSV endpoints.
| Asset | Total / 15m | Longs liquidated | Shorts liquidated | Dominant side | Confirmation |
|---|---|---|---|---|---|
| FIL · 29 events | $34,081.20 | $13,944.14 | $20,137.06 | short · 59.1% | Context only |
| CP · 8 events | $7,358.41 | $0.00 | $7,358.41 | short · 100.0% | Context only |
| TRUMP · 2 events | $7,334.70 | $7,334.70 | $0.00 | long · 100.0% | Context only |
| CASHCAT · 4 events | $5,862.57 | $5,862.57 | $0.00 | long · 100.0% | Context only |
| FLOCK · 13 events | $3,744.67 | $3,744.67 | $0.00 | long · 100.0% | Context only |
| ETHFI · 3 events | $3,023.75 | $3,023.75 | $0.00 | long · 100.0% | Context only |
| SIGN · 1 events | $2,254.34 | $2,254.34 | $0.00 | long · 100.0% | Context only |
| QTUM · 1 events | $1,031.03 | $1,031.03 | $0.00 | long · 100.0% | Context only |
| PONS · 1 events | $650.01 | $650.01 | $0.00 | long · 100.0% | Context only |
| PUMP · 3 events | $324.71 | $324.71 | $0.00 | long · 100.0% | Context only |
| GLM · 2 events | $310.46 | $310.46 | $0.00 | long · 100.0% | Context only |
| BLUR · 1 events | $252.31 | $252.31 | $0.00 | long · 100.0% | Context only |
| SENT · 2 events | $192.10 | $192.10 | $0.00 | long · 100.0% | Context only |
| GALA · 1 events | $184.50 | $184.50 | $0.00 | long · 100.0% | Context only |
| ZEC · 1 events | $108.79 | $0.00 | $108.79 | short · 100.0% | Context only |
| KAT · 1 events | $69.73 | $69.73 | $0.00 | long · 100.0% | Context only |
| BICO · 2 events | $41.09 | $41.09 | $0.00 | long · 100.0% | Context only |
| IOST · 1 events | $30.00 | $30.00 | $0.00 | long · 100.0% | Context only |
| CHZ · 1 events | $29.64 | $29.64 | $0.00 | long · 100.0% | Context only |
| LIT · 1 events | $24.44 | $24.44 | $0.00 | long · 100.0% | Context only |
Current source health
- okx liquidations: live; last success 2026-09-13 15:39:52 UTC
Observed OKX public-stream events only; not a whole-market liquidation total.
How to read this page
- Long liquidations are forced position exits during falling prices; they do not prove a bottom.
- Short liquidations involve forced buying during rising prices; they do not guarantee continued gains.
- The public table can show context-only activity while Telegram promotion requires stricter confirmation.
- The source scope, rolling window and stale state remain visible beside the figures.
What can this page tell you quickly?
- Best for
- Identifying which OKX perpetual assets have concentrated forced exits in the latest rolling 15-minute window.
- Strongest evidence
- Observed liquidation notional, liquidated side, event count and confirmation state come from one named public venue stream.
- Main limitation
- The totals are observed OKX events, not a modelled or aggregated estimate of all crypto liquidations.
- Next check
- Compare the forced exits with price, open interest, spot activity and nearby market structure before interpreting continuation or exhaustion.
What does crypto liquidation pressure mean?
A liquidation is a forced reduction or closure performed when a leveraged position no longer satisfies the venue's margin requirements. CoinNudge groups public OKX liquidation events by underlying asset and liquidated position side over the latest 15 minutes. The total indicates observed forced activity on this stream; it does not include ordinary stop losses, voluntary closes or every position that changed during the window.
Liquidation pressure matters because forced orders can add urgency to an existing move. Long liquidation involves closing a long position, normally adding sell-side pressure during a decline. Short liquidation involves closing a short position, normally adding buy-side pressure during a rise. The event describes what was forced out, not who will control the next move.
| Observed event | Mechanical effect | Possible context | Unsafe conclusion |
|---|---|---|---|
| Long liquidation | Leveraged long exposure is forcibly reduced | Downward move is pressuring long positions | The market has reached a bottom |
| Short liquidation | Leveraged short exposure is forcibly reduced | Upward move is pressuring short positions | The rally must continue |
| Mixed liquidations | Both sides are forced out in one window | Volatile or rapidly reversing conditions | One direction has clear control |
| No observed row | No valid event was retained for the window | A quiet stream or unavailable source | No liquidation occurred anywhere |
Verify: OKX liquidation-orders channel
How does CoinNudge calculate OKX liquidation notional?
OKX reports liquidation events with instrument and contract quantities. CoinNudge first calculates contract units as size × contract value × contract multiplier. For inverse contracts or contracts valued in USD, USDT or USDC, those units are the quote-notional estimate; otherwise valid base units are multiplied by bankruptcy price. Repeated events are deduplicated and explicit non-crypto underlyings are rejected before the 15-minute grouping.
Conversion is an estimate because contract specifications differ by instrument and market prices move. The page therefore labels the amount as observed notional rather than an accounting balance. If required instrument metadata is unavailable, a malformed event is not silently assigned a fabricated USD value. Source freshness is checked independently from whether the current window happens to be empty.
- Window: the latest rolling 15 minutes, not a UTC calendar bucket.
- Scope: OKX public perpetual liquidation events received by CoinNudge.
- Grouping: underlying asset and liquidated position side.
- Not included: ADL, normal stops, voluntary closes, other exchanges and on-chain lending protocols.
When does liquidation pressure qualify for a Telegram alert?
The website can show a valid observed cluster even when it remains context only. Telegram promotion is stricter. The current policy tests event notional against a dynamic reference built from the asset's available history, using an extreme percentile or a multiple of the recent median together with a USD floor. It also checks side concentration, matching price movement and supporting open-interest or spot-flow evidence.
This separation reduces messages caused by routine liquidations in an active contract. It cannot eliminate false interpretation: a large forced-exit cluster may accelerate, exhaust or be absorbed. A row marked 'alert qualified' means the documented evidence checks passed at evaluation time. It does not mean CoinNudge has predicted a reversal, continuation or profitable entry.
| Check | Why it is used | What failure means |
|---|---|---|
| Dynamic amount threshold | Separates unusual notional from an asset's recent background | The cluster remains website context |
| Dominant-side concentration | Avoids labelling a balanced burst as one-sided pressure | Direction is too mixed for promotion |
| Matching price movement | Checks whether forced exits align with the expected market move | Liquidation evidence and price disagree |
| OI or spot confirmation | Adds a separate positioning or executed-flow input | Supporting evidence is unavailable or insufficient |
How should long and short liquidation clusters be interpreted?
Read the cluster in sequence. First identify which side was liquidated and the dominant share. Then compare total notional with the number of events: one large event and many small events can have the same total but different microstructure. Next check price direction and OI. Falling price, long liquidations and falling OI together describe deleveraging more clearly than the liquidation amount alone.
After a cluster, monitor whether price accepts or rejects the affected area. Continued movement with new OI can mean leverage is rebuilding; a quick recovery with reduced OI can mean the forced move was absorbed. These are conditional interpretations, not automatic entries. A trader still needs an independent invalidation level, loss limit and executable-liquidity check.
- Use dominant share to distinguish one-sided pressure from a mixed window.
- Use event count to see whether notional is concentrated or distributed.
- Use OI to determine whether leverage is being removed or added around the move.
- Use spot flow to test whether unleveraged executed activity supports the direction.
- Do not infer total market liquidations by multiplying or extrapolating OKX observations.
Why can the OKX liquidation table be empty or stale?
An empty fresh window is a valid observation: CoinNudge may have received no qualifying OKX events during the latest 15 minutes. A stale state is different. It means the stream health check is older than the allowed freshness window, so absence cannot be interpreted as a quiet market. The interface distinguishes these conditions and does not replace unavailable activity with zero-filled rows.
WebSocket disconnects, exchange maintenance, network failures and instrument-metadata changes can delay or omit observations. The live page is therefore a monitoring aid, not an exchange-grade risk engine or sole liquidation-protection mechanism. Users managing leveraged positions should rely on their venue's margin information and independent risk controls.
Can I compare liquidation clusters without double-counting the same event?
Use event identities and non-overlapping windows where possible. Consecutive rolling 15-minute snapshots can contain many of the same forced closures, so adding their totals would exaggerate liquidation activity.
The OKX public stream is venue-specific and collection gaps limit historical completeness. A small total is not proof that the wider market experienced little liquidation.
- Choose either unique event aggregation or one consistent set of time windows.
- Keep long and short closures, contract conversion inputs and observation coverage separate.
- Align the cluster with price and OI observations from the same period before interpreting confirmation.
Verify: OKX liquidation-orders WebSocket · CoinNudge liquidation methodology
What is measured, and what is not?
| Measured claim | Evidence on this page | Boundary |
|---|---|---|
| OKX long or short positions were liquidated in the rolling window. | Deduplicated public liquidation events grouped by side. | The observation excludes other venues and non-public forced exits. |
| The displayed USD amount estimates observed liquidation notional. | Contract quantity converted with current instrument metadata. | It is not a whole-market total or an exchange account balance. |
| A cluster passed CoinNudge Telegram confirmation checks. | Amount, concentration, price and OI or spot-flow rules. | Qualification reports evidence, not future direction or profitability. |
Take the next step with this evidence.
Reading about okx crypto liquidations today: long vs short pressure? Choose ongoing notifications or a dataset you can inspect in your own research workflow.
Receive qualifying events in Telegram.
Use the ready-made alert checklist, message explanations and daily briefing. Check the supported categories and coins before subscribing; every Research page is not a separate alert category.
Check the alert list · View alert plans
Inspect the data before choosing a plan.
Market Events v1 connects recorded events and comparison rows with context, later outcomes and quality flags. Paid access provides customer API keys and daily JSON, CSV and Parquet files.
Check Market Events sample · Explore the full data catalog · Compare data plans
Researcher and Research Desk currently include Market Events v1 only, for its specified pairs and published history. This page's full dataset is not automatically included. Other data families require coverage, date, field and source-use confirmation before purchase. Telegram Pro and data access are separate subscriptions.
Method and data boundary
OKX events are deduplicated and grouped by crypto underlying and liquidated side over 15 minutes. Contract units equal size × contract value × contract multiplier. Inverse contracts and contracts whose value currency is USD, USDT or USDC use those units as quote notional; other valid contracts multiply units by bankruptcy price. Alert eligibility additionally requires amount, dominance, price and OI or spot-flow confirmation.
Explicit tokenized-equity and TradFi underlyings are excluded. The page does not include unreported events, ADL, normal stop losses, voluntary closes, on-chain lending liquidations or liquidation activity from other exchanges. A quiet window can legitimately contain no rows.
Sources and verification
- OKX liquidation-orders WebSocketOfficial public forced-liquidation event stream.
- CoinNudge liquidation methodologyContract conversion, dynamic thresholds and confirmation rules.
Frequently asked questions
Are these total crypto liquidations?
No. They are only events observed on the OKX public liquidation stream and will normally be lower than any responsibly aggregated multi-exchange total.
Why can the table be empty?
The rolling window may contain no valid OKX events, or the source may be temporarily stale. CoinNudge does not invent a zero-filled market event.
Do long liquidations mean Bitcoin or an altcoin has bottomed?
No. Long liquidation reports forced exits during a decline. The move can continue, reverse or consolidate depending on subsequent price, OI, liquidity and spot demand.
What does dominant-side share mean?
It is the percentage of observed liquidation notional attributed to the larger liquidated side in the 15-minute window. It helps distinguish one-sided from mixed pressure.
Why can a row say context only?
The observed event is valid but did not pass every Telegram promotion check, such as dynamic amount, side concentration, matching price and supporting OI or spot evidence.
How often does the liquidation page update?
The page requests a refreshed materialized snapshot about every 15 seconds. The underlying OKX WebSocket is monitored separately for freshness.
Get material leverage-pressure alerts in Telegram
CoinNudge promotes a liquidation event only after amount, side concentration, price and supporting OI or spot-flow checks pass.
Preview the Pro alert list