← Bitfinex status page

Bitfinex REST · ticker degradation, 4 min on 23 SEP 2026

Bitfinex REST · ticker — intermittently degraded: 2 episodes in the last hour, most recently p95 1636ms over the last five minutes, 31.5× the 7-day baseline of 52ms — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Bitfinex's public API on 23 SEP 2026 09:21 UTC. It lasted 4 min and ended 23 SEP 2026 09:26 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://api-pub.bitfinex.com/v2/ticker/tBTCUSD
DURATION
4 min
STARTED
23 SEP 2026 09:21 UTC
ENDED
23 SEP 2026 09:26 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 23 SEP 2026 09:21 UTC
    up24 opened the incident at degraded.
  2. 23 SEP 2026 09:26 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, 4 of 2,338 checks failed: timeout ×4.

— p50‑ ‑ p95
axis 0 – 5000ms
08:52 · 23 SEP09:24 · 23 SEP09:56 · 23 SEP

REST latency for the failing endpoint, per minute, from 23 SEP 2026 08:51 UTC to 23 SEP 2026 09:56 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.