crypto liquidations today
a running tally, not a headline. the figure below is every forced-close print our own collectors recorded in the trailing 24 hours — a rolling window that ends at the timestamp beside it, not a calendar day. what it counts, which venues are in it, and why it will not match another tracker's number are written out underneath.
- liquidated, trailing 24h
- $497,591,786
- forced-close prints
- 68,974
- which side got closed
- 90% long · 10% short
exported 2026-10-07 04:17 utc — the figures written into this page's html at build time
no live refresh yet — nothing on this page has been fetched from the api by your browser
hour by hour, oldest on the left · busiest: 2–3h ago, $390M
24h agonow
biggest single print: $26,643,802 ETH long on binance, 2026-10-07 02:01 utc
| venue | 24h usd | share |
|---|---|---|
| binance | $284M | 57.1% |
| hyperliquid | $83M | 16.8% |
| okx | $78M | 15.6% |
| bybit | $52M | 10.5% |
| coin | 24h usd | share of these 8 |
|---|---|---|
| ETH | $159M | 44.6% |
| BTC | $134M | 37.7% |
| ZEC | $15M | 4.1% |
| SOL | $13M | 3.8% |
| XRP | $12M | 3.5% |
| DOGE | $10M | 2.9% |
| SUI | $6.2M | 1.7% |
| PUMP | $6.1M | 1.7% |
okx and bybit dollars are bankruptcy-priced
the okx liquidation-orders feed and bybit's allLiquidation stream publish no fill price at all, only the bankruptcy price of the position, so an okx or bybit row's dollar figure is bankruptcy price × size while binance's and hyperliquid's are execution notionals. the cross-venue total above therefore mixes two price bases. there is no fill price to substitute, so it is left as it is and said out loud here.
what this number counts
one liquidation is one forced-close print: a position the venue closed itself because the margin behind it ran out, published on that venue's own liquidation feed. it lands here as one row — time, venue, coin, side, price, size — and nothing is typed in by hand.
the dollars are position notional, not trader losses. a $1m long at 20x is liquidated for $1m on this page while the account behind it lost the $50k of margin under it. every aggregate of this kind counts the notional, which is why the totals read the way they do; the events count next to it is the number of prints those dollars came from.
the window rolls. it is the 24 hours ending at the timestamp on the figure, recomputed from the tape each time it is refreshed — not midnight utc to now. "today" on this page means the last day of tape.
the long/short split is the side of the position that was closed, not the direction of the move: long liquidations are leveraged longs being sold out, short liquidations are shorts being bought back.
which venues are in the total
every print is read off a venue's own public feed rather than bought from an aggregator; binance and hyperliquid have been recorded here since 2026-09-19, and okx and bybit since 2026-09-23, with nothing before that date, so a window opening earlier holds no okx or bybit at all. the per-venue breakdown is the authority for what is in a given window — a venue missing from it is not a zero because the market was quiet there, it is a zero because nothing is listening to it.
bybit starts that late because the collector read bybit's allLiquidation frames against the wrong schema until 2026-09-23, so every earlier frame was dropped and there is no bybit history to backfill. its feed is subscribed per symbol and capped at fifty bases, so a liquidation on the fifty-first coin never enters the tape. binance's stream reduces coin-margined contracts to the base coin, so btcusd_perp prints land under btc rather than under a symbol of their own.
what is not in here at all: spot, margin desks and lending protocols. this is perpetual futures only. several other venues are polled on this site for funding rate and open interest — that is a different feed, and none of it reaches this total.
why this number differs from another tracker's
two sites can watch the same cascade and print different totals without either of them being wrong. these are the reasons ours is what it is.
binance thins its own liquidation feed
the all-market force-order stream publishes at most one message per symbol per second, and binance documents what that drops: "only the latest one liquidation order within 1000ms will be pushed as the snapshot". latest, not largest — whichever print the feed happens to sample at the end of that second is the one that survives, and the rest of the second is gone.
it thins hardest during exactly the conditions that bring anyone to a page like this, no per-row flag says what was lost, and the distortion runs one way. the binance share of this total is a lower bound, and so therefore is the total.
hyperliquid rows are reconstructed, not reported
hyperliquid publishes no liquidation stream. those rows are rebuilt from the public trades feed — a large print during a fast move — and carry an estimate flag in the database. they are counted in the total; they are not liquidations the venue itself declared.
venue set and window, before anything else
a tracker recording ten venues prints a bigger number than one recording a handful, at the same instant, from the same market. a tracker summing midnight-to-now prints a different number again from one summing a rolling 24 hours. compare the same venues over the same window or the comparison says nothing.
source: binance docs — all-market liquidation order streams (checked 2026-09-22)
nothing on this page is adjusted, extrapolated or smoothed to close those gaps. the tally is the tape; the gaps are the gaps.
what a 24h total is good for
it tells you that leverage on one side got cleared, and roughly when. it does not tell you where price goes next — forced closes remove positioning, they do not set direction — and it does not tell you whether your own position is next in line.
the distance between price and your liquidation is the number that does, and it is the one the alarm watches: telegram, push or email before the wick gets there, free, no signup.
where to go from here
set a liq alarm on your own position · where the next clusters sit · whether the cluster calls land
faq
how much crypto has been liquidated today?
the figure at the top of this page: the sum of every forced-close print our collectors recorded in the trailing 24 hours, in position notional, with the end of that window timestamped beside it. it refreshes from the api while the page is open.
what does 'today' mean on this page?
the last 24 hours of tape, ending at the timestamp on the figure — a rolling window, not midnight utc to now. the hourly bars are offsets into that window, so the rightmost bar is the hour that just ended.
what counts as a liquidation?
a position the venue force-closed because the margin behind it ran out, published on the venue's public liquidation feed. the dollar figure is the notional of the position closed, not what the trader lost — a $1m long at 20x counts as $1m here and cost its owner $50k of margin.
why do liquidation totals differ between sites?
different venue sets, different windows, and different feeds. binance's public stream pushes at most one liquidation per symbol per second, so any figure drawn from it is a lower bound; venues that publish no liquidation stream have to be reconstructed; and a rolling 24 hours is not the same window as a calendar day.
is this the real total for the whole market?
no. it is the total of what these collectors recorded, and it is a lower bound: binance's own documentation says only the latest liquidation order within 1000ms is pushed, so prints are dropped exactly during cascades. treat it as a floor under the day, not a census of it.
does a big liquidation day mean price reverses?
no. a cascade clears leveraged positioning on one side; it is a record of what already happened to other people's margin, not a signal about what happens next. the split tells you which side got cleared, and that is all it tells you.