Skip to content
PerpFinder

CEX Perp Volume vs Observable Depth, Q3 2026

PerpFinder editorial · Published

From 2026-09-12 12:00 UTC to 2026-09-23 06:00 UTC, PerpFinder stored 44 volume-quality sweeps under methodology version 3. In the latest sweep, 20 centralized perpetual venues reported $243.3 billion of 24-hour volume. 99.8 percent of the stored venue rows reached the $1,000,000 top of the standardized ladder, so the reported-to-support ratio ranks venues mostly by reported turnover and not by depth. The daily snapshots from 2026-07-01 to 2026-09-21 hold 28 venue-days above the 3× spike rule. This issue covers part of the quarter.

Period (UTC)2026-07-01 00:00 UTC2026-09-23 06:00 UTC
Published2026-09-23
Max samples/series886
Min completeness75.0%
Facts / suppressed27 / 0

Measurements of publicly observable data, never accusations. A high reported-to-support ratio means reported activity is large relative to visible book depth at standardized sizes, and nothing more. This report does not claim that any venue misreports volume.

What this report measures

PerpFinder collects two independent measurements every 6 hours. The first measurement is the 24-hour perpetual volume that each venue reports on its own ticker endpoint. The second measurement is the visible order book of the venue, walked by the PerpFinder cost engine at standardized order sizes. The volume-quality dataset stores both measurements with the sweep clock. The full rule set is on the volume-quality methodology page.

This report covers the third quarter of 2026, from 2026-07-01 to 2026-09-30. PerpFinder published it on 2026-09-23, before the quarter ended. The last sweep it uses is 2026-09-23 06:00 UTC, so the report covers part of the quarter.

The ratio figures use methodology version 3 only. That version holds 44 stored sweeps from 2026-09-12 12:00 UTC to 2026-09-23 06:00 UTC. The quarter also holds sweeps of version 1 and version 2. PerpFinder never merges two versions, so those sweeps appear only in the versions table.

What the ratio does and does not mean

The reported-to-support ratio divides the reported BTC and ETH perpetual volume of a venue by the largest standardized order that its book absorbed in the same sweep. A high ratio means the venue reported a large amount of turnover next to a small measured order size.

A low or high ratio is a measurement of visible depth against reported turnover. It is not a finding of misreporting. This report does not claim that any venue misreports its volume, and the dataset makes no such claim either.

Ordinary market structure produces high ratios. Market makers recycle the same inventory many times each day, so real turnover can exceed the depth that is visible at any single instant. A venue can also keep size off the visible book and add it when a large order arrives.

Observation 1: the latest sweep

In the 2026-09-23 06:00 UTC sweep, 20 centralized perpetual venues reported $243.3 billion of 24-hour volume. 15 of those venues publish a BTC and ETH breakdown, and their main markets hold $91.1 billion.

The ratio runs from 366 at BloFin to 23,232 at Binance, with a median of 5,017.

5 venues produced no ratio. Those venues publish no per-symbol breakdown that the feed can use, so their main-market volume stays null. A missing value stays null and never becomes zero.

Reported volume and observable signals, latest sweep

Measured at 2026-09-23 06:00 UTC sweep · PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history

Ratio = reported BTC and ETH perpetual volume ÷ the largest standardized order the venue absorbed in the same sweep. A venue with no usable per-symbol breakdown keeps a null main-market figure and a null ratio. Download this table as CSV

VenueReported 24h ($M)BTC+ETH markets ($M)Median spread (bps)Slippage at $100k (bps)Largest fill ($M)RatioPercentileData confidence
Binance74080.223231.60.02012323297100
OKX27499.70.020180
Toobit18814.99972.60.0201997383100
Bybit18076.18969.10.0201896977100
WEEX1686050170.0201501750100
Gate.io16144.412227.80.02011222890100
MEXC11819.85131.30.0201513157100
WhiteBIT10111.85400.90.761.11540163100
XT.COM98100.040180
Coinbase9438.78897.10.0201889770100
Bitget8875.14510.50.0201451143100
BingX6745.415710.210.031157130100
Bitunix6512.73921.80.0201392237100
KuCoin2600.40.530.93180
Deribit1360.70.120.48180
HTX1356.31097.10.020.031109723100
Kraken1045.70.780.56180
BloFin841.1365.70.02013663100
Phemex834.7442.80.020.15144317100
Crypto.com442.4382.30.51.58138210100

Scroll the columns sideways to see every field. The CSV holds the same rows.

Observation 2: the standardized ladder stops at $1 million

Across the 44 stored sweeps, 884 of 886 venue rows record a largest absorbed order of $1,000,000, which is 99.8 percent. The ladder has no larger rung.

The denominator of the ratio is therefore almost constant, and the ratio ranks venues mostly by reported main-market volume. A reader who wants a depth ranking must use the larger order sizes in the cost comparison tool.

Observation 3: a single sweep does not describe a venue

14 venues produced a ratio in every one of the 44 sweeps. No venue kept its ratio inside a 2× band across the window.

The tightest venue is MEXC, which moved between 2,320 and 8,378, a factor of 3.6. The widest venue is WhiteBIT, which moved between 590 and 50,567, a factor of 85.7. The median venue moved by a factor of 6.3.

Use the median across many sweeps to compare venues. Treat a single sweep as one moment in a moving series.

Stored sweeps · ratio, log scale

Reported-to-support ratio: range across sweeps

Lowest to highestMedian
Binance23,242
Gate.io11,775
Toobit10,957
Bybit8,868
Coinbase7,926
MEXC5,914
WEEX5,709
WhiteBIT5,170
Bitget4,621
Bitunix4,140

Log scale: 10 to 50,567 · displayed value is the median · a ratio is a measurement, not a finding about a venue

First 10 rows in the published table order; 16 venues in the full table. 2026-09-12 12:00 UTC to 2026-09-23 06:00 UTC (44 stored sweeps, methodology version 3). Median, minimum and maximum of the ratio of each venue across every stored sweep of the version. The spread column divides the maximum by the minimum. The two cost columns are the median of the stored sweeps. Source: PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history. The data table contains the plotted values.

Reported-to-support ratio across the stored sweeps

Measured at 2026-09-12 12:00 UTC to 2026-09-23 06:00 UTC (44 stored sweeps, methodology version 3) · PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history

Median, minimum and maximum of the ratio of each venue across every stored sweep of the version. The spread column divides the maximum by the minimum. The two cost columns are the median of the stored sweeps. Download this table as CSV

VenueSweepsMedian ratioMinimumMaximumMaximum ÷ minimumMedian spread (bps)Median slippage at $100k (bps)
Binance44232426096411576.80.030
Gate.io44117752406200738.30.030.01
Toobit44109574511173873.90.030
Bybit4488681944144087.40.030.06
Coinbase4479268511010411.90.030
MEXC445914232083783.60.030
WEEX37570983110803130.030
WhiteBIT4451705905056785.72.821.39
Bitget4446211327794060.030.05
Bitunix44414099466746.70.030.02
Bitmart626201810112046.20.030
BingX441545467278160.180.07
HTX441160370220460.030
Crypto.com444541245684.62.122.14
Phemex444181205764.80.030.34
BloFin443871168797.60.160

Scroll the columns sideways to see every field. The CSV holds the same rows.

Observation 4: reported volume above the 3× spike rule

PerpFinder flags a venue when its reported 24-hour volume passes 3× the median of its own previous seven stored days. A flagged venue stays visible and leaves the headline market total until the figure holds.

The 83 daily snapshots from 2026-07-01 to 2026-09-21 hold 28 centralized venue-days above the rule, across 15 venues. 22 of them fall on the 26 reconstructed days. A reconstructed day reads a different instant than a captured day, so part of that multiple is a change of clock.

A flag marks a figure that needs a second day to confirm it. It is not a statement about the venue.

Reported 24h volume above the 3× spike rule

Measured at daily snapshots 2026-07-01 to 2026-09-21 · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history

A venue-day enters this table when the venue reported more than 3× the median of its own previous seven stored days. A flagged venue stays visible on the site and leaves the headline market total until the figure holds. The day column states whether the day was captured or reconstructed. Download this table as CSV

VenueDateDayReported 24h ($M)7-day median ($M)Multiple
Bitmart2026-07-16captured24053.76424.23.7
WhiteBIT2026-08-16reconstructed29240.77535.13.9
Deribit2026-08-20reconstructed1255.2230.85.4
Bitmart2026-08-20reconstructed25869.84989.35.2
Kraken2026-08-20reconstructed1775.6461.23.8
BloFin2026-08-20reconstructed1722.1548.63.1
KuCoin2026-08-20reconstructed3314.71072.73.1
Bybit2026-08-20reconstructed25243.48204.33.1
HTX2026-08-20reconstructed3286.91069.73.1
Deribit2026-08-21reconstructed1434.1230.86.2
Kraken2026-08-21reconstructed1772.6461.23.8
Bitmart2026-08-21reconstructed16152.54989.33.2
Deribit2026-08-22reconstructed2129.2265.88
Bitmart2026-08-22reconstructed34346.64989.36.9
Kraken2026-08-22reconstructed3020.7461.26.5
KuCoin2026-08-22reconstructed4317.51072.74
BloFin2026-08-22reconstructed2092.3563.63.7
Crypto.com2026-08-22reconstructed1155.5330.73.5
Bybit2026-08-22reconstructed28648.68204.33.5
XT.COM2026-08-22reconstructed15750.34781.13.3
HTX2026-08-22reconstructed3658.91165.23.1
OKX2026-08-22reconstructed51511.916824.33.1
Bitget2026-08-22reconstructed186276090.23.1
WEEX2026-09-04captured90471.47626.511.9
Backpack2026-09-10captured397.6118.83.3
BitMEX2026-09-16captured182.28.4
WhiteBIT2026-09-19captured51186.36709.97.6
WEEX2026-09-19captured44273.912280.23.6

Scroll the columns sideways to see every field. The CSV holds the same rows.

What this report rests on

The ratio figures rest on 44 sweeps, 44 of them complete, with between 20 and 21 venues per sweep. The spike figures rest on 83 stored days: 57 captured and 26 reconstructed.

The volume-quality series starts on 2026-07-16, so the quarter holds no sweep before that day. The public API serves at most 30 days, so this report read the sweeps from 2026-08-24 only. Earlier sweeps of older versions are not in the versions table.

The daily snapshots in the repository end on 2026-09-21. Later days are in the runtime store and are not in this report.

Volume-quality methodology versions inside 2026-Q3

Measured at sweeps read from 2026-08-24 to 2026-09-23 06:00 UTC · PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history

PerpFinder stores each methodology version apart and never merges two versions. The ratio figures of this report use one version. The public API serves at most 30 days, so the table counts only the sweeps inside that read window. Download this table as CSV

VersionFirst sweep readLast sweep readSweeps readCompleteUsed for ratios
12026-08-25 00:00 UTC2026-09-03 18:00 UTC4040no
22026-09-04 00:00 UTC2026-09-12 06:00 UTC3434no
32026-09-12 12:00 UTC2026-09-23 06:00 UTC4444yes

Scroll the columns sideways to see every field. The CSV holds the same rows.

Limitations

Each venue API returns a limited depth page. When a walk reaches the end of that page, the row records the limit, and the venue may hold more size than the measurement shows.

The engine walks the buy side only. A one-sided walk does not describe the sell side of the same book.

The sweep cadence is 6 hours, and each walk is one instant. Depth changes between sweeps, and a later sweep returns different numbers.

Reported volume comes from the ticker endpoint of each venue. PerpFinder normalizes the unit and the market type, and does not audit the venue figure.

How to reproduce these numbers

Every number comes from public endpoints that need no key. The sweep figures come from https://perpfinder.com/api/data/volume-quality-history?days=30&methodologyVersion=3. The spike figures come from https://perpfinder.com/api/data/venue-history?venue=Binance&days=30, the same endpoint for each venue, and the stored daily snapshots.

Those endpoints serve the current state, so a later call returns later numbers. Each table on this page carries a CSV with the exact rows of this report, and the fact block carries a CSV of every headline figure.

Updates

PerpFinder keeps no fixed publication schedule for this series. A published report is not edited after publication. A report on a later window is published as a new page, and the sweeps continue every 6 hours in the meantime.

The numbers

MetricValue
Stored sweeps of methodology version 3 inside 2026-Q3PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history44
Stored sweeps with status completePerpFinder stored volume-quality sweeps — /api/data/volume-quality-history44
Fewest venues in one stored sweepPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history20
Most venues in one stored sweepPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history21
Venues in the 2026-09-23 06:00 UTC sweepPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history20
Reported 24h perpetual volume, all venues in the 2026-09-23 06:00 UTC sweep (USD billion)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history243.3
Reported BTC and ETH main-market volume, venues with a published breakdown (USD billion)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history91.1
Venues with a reported-to-support ratio in the latest sweepPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history15
Venues with no usable per-symbol breakdown, so no ratioPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history5
Median per-venue reported-to-support ratio in the latest sweepPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history5,017
Lowest per-venue ratio in the latest sweep (BloFin)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history366
Highest per-venue ratio in the latest sweep (Binance)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history23,232
Stored venue rows whose largest absorbed order equals the $1,000,000 ladder topPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history884
Stored venue rows with a largest absorbed orderPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history886
Share of stored venue rows at the $1,000,000 ladder top (percent)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history99.8
Venues with a ratio in every stored sweepPerpFinder stored volume-quality sweeps — /api/data/volume-quality-history14
Venues whose ratio stayed inside a 2× band (maximum ÷ minimum at most 2)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history0
Median venue ratio spread (maximum ÷ minimum)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history6.3
Tightest ratio spread (MEXC, maximum ÷ minimum)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history3.6
Widest ratio spread (WhiteBIT, maximum ÷ minimum)PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history85.7
Stored daily snapshots from 2026-07-01 to 2026-09-21PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history83
Stored days reconstructed after the fact instead of capturedPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history26
Stored days captured on the dayPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history57
Centralized venue-days above the 3× spike rulePerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history28
Centralized venues with at least one venue-day above the rulePerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history15
Venue-days above the rule that fall on a reconstructed dayPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history22
Spike rule multiple of the venue own 7-day medianPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history3

Author: PerpFinder editorial — the PerpFinder data desk. Published research carries the desk byline. Send a correction through the corrections page.

Sources: PerpFinder stored volume-quality sweeps — /api/data/volume-quality-history · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history

Facts are generated deterministically from PerpFinder’s self-collected datasets (frozen methodology, versioned for each reported series) and are never edited by hand — only the narrative around them is editorial. Republishing the numbers is welcome with attribution: data license.