← Bitfinex status page

Bitfinex REST · ticker degradation, ongoing since 26 OCT 2026

Bitfinex REST · ticker — p95 715ms over the last five minutes, 6.8× the 7-day baseline of 105ms — from Carlstadt, US only; 2 regions had too little evidence. up24 opened this incident from its own measurements of Bitfinex's public API on 26 OCT 2026 23:04 UTC. It is still open, 2h 29m in.

DEGRADEDREST · ticker · https://api-pub.bitfinex.com/v2/ticker/tBTCUSD
DURATION
2h 29m
STARTED
26 OCT 2026 23:04 UTC
ENDED
ONGOING
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 26 OCT 2026 23:04 UTC
    up24 opened the incident at degraded.

HOW IT FAILED

Over the window, 0 of 2,180 checks failed.

— p50‑ ‑ p95
axis 0 – 1000ms
20:36 · 26 OCT21:48 · 26 OCT23:00 · 26 OCT

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 26 OCT 2026 20:35 UTC to 27 OCT 2026 01:33 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 68 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 — 1 recorded transitions — and nothing on it is reported by Bitfinex.