← Bitfinex status page

Bitfinex REST · ticker degradation, 2 min on 21 OCT 2026

Bitfinex REST · ticker — p95 554ms over the last five minutes, 5.7× the 7-day baseline of 98ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Bitfinex's public API on 21 OCT 2026 16:03 UTC. It lasted 2 min and ended 21 OCT 2026 16:05 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://api-pub.bitfinex.com/v2/ticker/tBTCUSD
DURATION
2 min
STARTED
21 OCT 2026 16:03 UTC
ENDED
21 OCT 2026 16:05 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 21 OCT 2026 16:03 UTC
    up24 opened the incident at degraded.
  2. 21 OCT 2026 16:05 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.

HOW IT FAILED

Over the window, 0 of 2,232 checks failed: no error class was recorded against them.

— p50‑ ‑ p95
axis 0 – 1000ms
15:34 · 21 OCT16:04 · 21 OCT16:35 · 21 OCT

REST latency for the failing endpoint, per minute, from 21 OCT 2026 15:33 UTC to 21 OCT 2026 16:35 UTC. The gap in the line is where nothing answered.

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 65 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.