← Bitfinex status page

Bitfinex REST · ping degradation, 50s on 10 SEP 2026

Bitfinex REST · ping — 100% of checks failing over the last minute (timeout) — from Singapore, SG and Lauterbourg, FR — re-graded on 12 Sep 2026: an outage grade now needs two minutes, and this lasted 50 seconds. up24 opened this incident from its own measurements of Bitfinex's public API on 10 SEP 2026 10:09 UTC. It lasted 50s and ended 10 SEP 2026 10:10 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api-pub.bitfinex.com/v2/platform/status
DURATION
50s
STARTED
10 SEP 2026 10:09 UTC
ENDED
10 SEP 2026 10:10 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 10 SEP 2026 10:09 UTC
    up24 opened the incident at degraded, timeout.
  2. 10 SEP 2026 10:10 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, 3 of 1,464 checks failed: timeout ×379.

— p50‑ ‑ p95
axis 0 – 2000ms
09:40 · 10 SEP10:10 · 10 SEP10:40 · 10 SEP

REST latency for the failing endpoint, per minute, from 10 SEP 2026 09:39 UTC to 10 SEP 2026 10:40 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.