Which crypto exchange stays online when the market moves?
We check 10 exchanges every 15 seconds from one fixed location and publish every measurement — including the numbers exchanges never report about themselves.
Among 10 exchanges measured from Tokyo, JP, Binance has the highest API availability on record (99.994%) and Binance the fastest median response (5 ms).
Exchange API reliability report: October 2026Crypto exchange API status, ranked
Ranked by availability, then by median response time.
| Exchange | Availability | Uptime | Median | p95 | Clock offset | Data age | Status |
|---|---|---|---|---|---|---|---|
|
1
|
|
99.994% | 5 ms | 8 ms | −2 ms | 18 ms | Operational |
|
2
|
|
99.994% | 75 ms | 100 ms | −1 ms | 6 ms | Operational |
|
3
|
|
99.992% | 6 ms | 103 ms | −2 ms | ≈0 ms | Operational |
|
4
|
|
99.992% | 22 ms | 51 ms | ±0 ms | 10 ms | Operational |
|
5
|
|
99.990% | 15 ms | 32 ms | ±0 ms | 696 ms | Operational |
|
6
|
|
99.980% | 127 ms | 258 ms | ±0 ms | 1,125 ms | Operational |
|
7
|
|
99.971% | 18 ms | 52 ms | ±0 ms | ≈0 ms | Operational |
|
8
|
|
99.79% | 252 ms | 482 ms | +2 ms | ≈0 ms | Degraded |
|
9
|
|
99.62% | 31 ms | 207 ms | +2 ms | 815 ms | Degraded |
|
10
|
|
97.7% | 14 ms | 68 ms | +1 ms | ≈0 ms | Failing |
What exchange status pages leave out
Three numbers you will not find on any exchange's own status page.
Clock offset
How far an exchange's server clock sits from the median of all the exchanges we measure. Your order timestamps, funding settlements and API rate limits are all stamped by that clock.
All 10 exchanges sit within 2 ms of each other. No exchange's clock is measurably drifting.
Market-data age
How old a price quote already is at the moment the exchange hands it to you, by the exchange's own clock. A stale quote is the gap between the price you see and the price you get.
Coinbase — stalest · Bitget ≈0 ms — freshest
Uptime under stress
Availability measured only during the busiest 5-minute stretches on record — currently the ones where the Bitcoin price moved at least 0.19%. That threshold follows the market rather than staying fixed: a fixed one never triggers in a calm week and lets noise through in a wild one. Uptime measured only while the market is quiet tells you very little.
HTX — 68,853 checks
Recent incidents
An incident opens after 2 failed checks in a row and closes after 2 good ones in a row.
| Exchange | When | Service | Cause | Duration | Status |
|---|---|---|---|---|---|
| 2026-11-09 12:56 | Order book | Exchange reported an error | 30s | Failing | |
| 2026-11-09 05:18 | Market data | Exchange reported an error | 30s | Failing | |
| 2026-11-09 03:50 | Market data | Exchange reported an error | 30s | Failing | |
| 2026-11-09 00:45 | Market data | Exchange reported an error | 30s | Failing | |
| 2026-11-08 22:55 | Market data | Exchange reported an error | 30s | Failing | |
| 2026-11-08 22:24 | Market data | Exchange reported an error | 30s | Failing | |
| 2026-11-08 21:29 | Order book | Exchange reported an error | 30s | Failing | |
| 2026-11-08 20:36 | Order book | Exchange reported an error | 45s | Failing | |
| 2026-11-08 18:06 | Server time | Request timed out | 45s | Failing | |
| 2026-11-08 18:06 | Market data | Request timed out | 45s | Failing | |
| 2026-11-08 18:06 | Server time | Request timed out | 1m 0s | Failing | |
| 2026-11-08 18:06 | Order book | Request timed out | 1m 0s | Failing |