Which Crypto Exchanges Are Monitored, and Where the Data Comes From

Monitored exchanges and their sources

Figures below are catalog observations, not live prices, volumes, or a ranking.

The radar currently monitors 15 centralized exchanges. Each row shows how many public sources feed the venue and how much of its catalog the radar currently observes. A dash means that category is not collected for that venue.

Every exchange page lists its exact source URLs. Typical sources are a venue’s public symbol or instrument list, its currency and chain list, and its published API changelog or OpenAPI document.

How collection works

1. A scheduled job fetches each venue’s public, unauthenticated endpoints once a day. There is no login, API key, or order-book access.
2. Responses are parsed into facts (an asset, a trading pair, a network rail, an API capability) with a status, the source it came from, and the time it was observed.
3. Facts are compared with the previous collection. Only real differences become detected changes; noisy fields such as fees, precisions and limits are ignored.
4. Results are published as a static snapshot, and every page on this site is built from it.

How the numbers are counted

Asset, pair and network counts include what a venue currently offers. Limited entries (limit-only markets, one open deposit or withdrawal rail) are counted; delisted, halted and unavailable entries are kept as history but excluded. A venue’s own spelling of an asset or network (for example Kraken’s XXBT, or ETH versus Ethereum versus ERC20) is matched to a shared name only for lookups; stored facts keep the venue’s own ids.

A count is a catalog statement. It says nothing about volume, liquidity, fees, custody, or whether a product is available in your country. Read the disclaimer before using any figure.

What can go wrong, and how it is handled

• A source fails or blocks the collector. The last good facts stay in place and the failure is shown on the exchange page.
• A response collapses. If a catalog suddenly parses to less than half of what it contained, it is ignored and retried rather than recorded as a mass delisting.
• A venue publishes no network data. Deposit and withdrawal coverage is then “not collected”, never “unsupported”.

Sources whose latest attempt failed right now: Bybit (api.bybit.com, 11 Nov 2026, 13:39); Bybit (api.bybit.com, 11 Nov 2026, 13:39). Their figures are from the last successful collection.

What is deliberately not tracked

Prices, trading volume, liquidity, maker and taker fee schedules, KYC and country availability, proof of reserves, regulatory status, and DEX pools are outside this dataset. See the fees guide and the research checklist for how to verify those on the venue itself.