← Bitfinex status page

Bitfinex REST · ping degradation, 12 min on 11 SEP 2026

Bitfinex REST · ping — p95 1275ms over the last five minutes, 4.3× the 7-day baseline of 295ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Bitfinex's public API on 11 SEP 2026 23:30 UTC. It lasted 12 min and ended 11 SEP 2026 23:42 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api-pub.bitfinex.com/v2/platform/status
DURATION
12 min
STARTED
11 SEP 2026 23:30 UTC
ENDED
11 SEP 2026 23:42 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 11 SEP 2026 23:30 UTC
    up24 opened the incident at degraded.
  2. 11 SEP 2026 23:42 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 1,728 checks failed: timeout ×449.

— p50‑ ‑ p95
axis 0 – 5000ms
23:01 · 11 SEP23:36 · 11 SEP00:12 · 12 SEP

REST latency for the failing endpoint, per minute, from 11 SEP 2026 23:00 UTC to 12 SEP 2026 00:12 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.