Carlo-fillbench/exchange-api-latency

Crypto Exchange REST API Latency Benchmark

Open, reproducible latency benchmark for the public REST APIs of major crypto exchanges: Coinbase, Kraken, Gemini, Crypto.com, Bitfinex, and KuCoin.

Live site and full context: fillbench.com/exchange-api-latency

How it is measured

Each run holds one persistent keep-alive HTTPS connection per exchange, warms it up, then times back-to-back GET requests to a small public market-data endpoint (no API keys, no auth, no orders). The one-time TLS handshake is timed separately as connect_ms and kept out of the request latency. Any non-200 or error is excluded from the stats and counted separately.

Every run executes from the same fixed US East server. That fixed vantage point is the point: it keeps the comparison between exchanges stable from run to run instead of drifting with whatever cloud region hosted the test. Read the numbers as a fair relative ranking from one consistent US vantage point. Full method: fillbench.com/methodology.

Fields

Per venue, per run: min / p50 / p95 / p99 / max / mean request latency in milliseconds, TLS connect_ms, samples_ok, errors, and a US-reachability flag. history.json holds a rolling daily p50/p95 time series per venue.

Cadence

The benchmark reruns every 2 hours. This mirror is refreshed daily. The freshest single run is always at fillbench.com/data/latency-latest.json.

License and attribution

Released under CC BY 4.0. Free to use, share, and build on, including commercially, with credit.

Attribution: Latency data by FillBench (https://fillbench.com), CC BY 4.0.

Cite as: FillBench. "Crypto Exchange REST API Latency Benchmark." https://fillbench.com/exchange-api-latency