← Bitfinex status page

Bitfinex REST · ping degradation, 3 min on 06 OCT 2026

Bitfinex REST · ping — p95 512ms over the last five minutes, 4.9× the 7-day baseline of 105ms — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Bitfinex's public API on 06 OCT 2026 17:02 UTC. It lasted 3 min and ended 06 OCT 2026 17:05 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api-pub.bitfinex.com/v2/platform/status
DURATION
3 min
STARTED
06 OCT 2026 17:02 UTC
ENDED
06 OCT 2026 17:05 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 06 OCT 2026 17:02 UTC
    up24 opened the incident at degraded.
  2. 06 OCT 2026 17: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, 292 of 2,236 checks failed: timeout ×292.

— p50‑ ‑ p95
axis 0 – 5000ms
16:33 · 06 OCT17:04 · 06 OCT17:35 · 06 OCT

REST latency for the failing endpoint, per minute, from 06 OCT 2026 16:32 UTC to 06 OCT 2026 17: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 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.