← Bitfinex status page

Bitfinex WS · trade degradation, 5 min on 16 AUG 2026

Bitfinex WS · trade — 33% of windows stalled over the last minute (stalled). up24 opened this incident from its own measurements of Bitfinex's public API on 16 AUG 2026 07:20 UTC. It lasted 5 min and ended 16 AUG 2026 07:25 UTC, when the component started answering again.

DEGRADEDWS · trade · trades
DURATION
5 min
STARTED
16 AUG 2026 07:20 UTC
ENDED
16 AUG 2026 07:25 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 16 AUG 2026 07:20 UTC
    up24 opened the incident at degraded, stalled.
  2. 16 AUG 2026 07:25 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.

HOW IT FAILED

Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.

— p50‑ ‑ p95
axis 0 – 200ms
06:51 · 16 AUG07:23 · 16 AUG07:55 · 16 AUG

A stream has no latency of its own — a feed either delivers or it does not — so this is Bitfinex's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

DID BITFINEX SAY SO?

Bitfinex publishes a status feed and nothing in it lines up with this incident. That is not proof they stayed silent; it is what their feed says.

up24 opened 62 incidents for Bitfinex in the last 90 days. Nothing Bitfinex published lines up with any of them.

BITFINEX — OTHER INCIDENTS

Measured by up24's own probe against Bitfinex's public API, tBTCUSD against USD, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by Bitfinex.