← Bitfinex status page

Bitfinex REST · ticker degradation, 2 min on 11 SEP 2026

Bitfinex REST · ticker — p95 621ms over the last five minutes, 8.2× the 7-day baseline of 76ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Bitfinex's public API on 11 SEP 2026 19:37 UTC. It lasted 2 min and ended 11 SEP 2026 19:39 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://api-pub.bitfinex.com/v2/ticker/tBTCUSD
DURATION
2 min
STARTED
11 SEP 2026 19:37 UTC
ENDED
11 SEP 2026 19:39 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 11 SEP 2026 19:37 UTC
    up24 opened the incident at degraded.
  2. 11 SEP 2026 19:39 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, 1 of 1,488 checks failed: timeout ×270.

— p50‑ ‑ p95
axis 0 – 2000ms
19:08 · 11 SEP19:38 · 11 SEP20:09 · 11 SEP

REST latency for the failing endpoint, per minute, from 11 SEP 2026 19:07 UTC to 11 SEP 2026 20:09 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 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.