← Bitfinex status page

Bitfinex REST · ping degradation, 4 min on 13 SEP 2026

Bitfinex REST · ping — p95 579ms over the last five minutes, 13.2× the 7-day baseline of 44ms — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Bitfinex's public API on 13 SEP 2026 17:44 UTC. It lasted 4 min and ended 13 SEP 2026 17:48 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api-pub.bitfinex.com/v2/platform/status
DURATION
4 min
STARTED
13 SEP 2026 17:44 UTC
ENDED
13 SEP 2026 17:48 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 13 SEP 2026 17:44 UTC
    up24 opened the incident at degraded.
  2. 13 SEP 2026 17:48 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 2,302 checks failed: timeout ×1.

— p50‑ ‑ p95
axis 0 – 5000ms
17:15 · 13 SEP17:46 · 13 SEP18:18 · 13 SEP

REST latency for the failing endpoint, per minute, from 13 SEP 2026 17:14 UTC to 13 SEP 2026 18:18 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.