← reliability leaderboard

Bitfinex vs Bitstamp: which API is more reliable?

Over the 60 days of a 90-day window up24 has measured so far, Bitfinex was more available — 99.99% against 99.96% of checks answered, and Bitfinex was quicker — a typical p95 of 59ms against 145ms.

Both venues are probed by the same probes on the same schedule — 90-day window, one request every 5 seconds, percentiles over successful responses only and measured from Lauterbourg, FR. Neither exchange reports any of this; up24 measures it.

MEASUREMENT
Bitfinex
tBTCUSD
OPERATIONAL
Bitstamp
btcusd
OPERATIONAL
Uptime · 90d
99.99%99.96%
REST checks behind it
3,082,6813,053,129
Days measured
62 of 9060 of 90
Typical p50
20ms (better)34ms
Typical p95
59ms (better)145ms
Worst day
99.90%99.80%
up24 incidents · 90d
62189
WS delivering · 24h
99.93%100.00% (better)
WS connected · 24h
99.99%100.00% (better)
Reconnects · 24h
320 (better)
Sequence gaps · 24h
00
Longest feed silence · 24h
51s (better)1 min 35s
Own status feed
statuspagestatuspage
Incidents they acknowledged
0 of 627 of 189
Median gap to their own notice
—1h 34m later

BITFINEX

Over the 62 days of a 90-day window up24 has measured so far, Bitfinex's REST API answered 99.99% of 3,082,681 checks, with a typical p95 of 59ms and a typical p50 of 20ms. Its worst day was 31 AUG 2026, at 99.90%. up24 opened 62 incidents against it in that window — uptime counts REST checks only, and an incident is as often a WebSocket feed that stalled or a socket that dropped.

Over the last 24 hours Bitfinex's WebSocket feeds were delivering 99.93% of the time on a socket up24 held open 99.99% of it, across 32 reconnects, with 0 sequence gaps and a longest silence of 51s.

Bitfinex status page → Is Bitfinex down? →

BITSTAMP

Over the 60 days of a 90-day window up24 has measured so far, Bitstamp's REST API answered 99.96% of 3,053,129 checks, with a typical p95 of 145ms and a typical p50 of 34ms. Its worst day was 19 AUG 2026, at 99.80%. up24 opened 189 incidents against it in that window — uptime counts REST checks only, and an incident is as often a WebSocket feed that stalled or a socket that dropped.

Over the last 24 hours Bitstamp's WebSocket feeds were delivering 100.00% of the time on a socket up24 held open 100.00% of it, across 0 reconnects, with 0 sequence gaps and a longest silence of 1 min 35s.

Bitstamp status page → Is Bitstamp down? →

Uptime is ok checks over total checks, REST only. Both percentiles are medians of daily percentiles over the window rather than the window's own — percentiles do not compose, and the daily rollup is the finest grain that outlives raw retention. Green marks the better column on that row and nothing else: a venue with no measurement never wins one.