← Bitfinex status page

Bitfinex REST · ping degradation, 40s on 20 AUG 2026

Bitfinex REST · ping — p95 272ms over five minutes, 7× the 7-day baseline of 39ms. up24 opened this incident from its own measurements of Bitfinex's public API on 20 AUG 2026 14:09 UTC. It lasted 40s and ended 20 AUG 2026 14:09 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api-pub.bitfinex.com/v2/platform/status
DURATION
40s
STARTED
20 AUG 2026 14:09 UTC
ENDED
20 AUG 2026 14:09 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 20 AUG 2026 14:09 UTC
    up24 opened the incident at degraded.
  2. 20 AUG 2026 14:09 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 718 checks failed: timeout ×1.

— p50‑ ‑ p95
axis 0 – 1000ms
13:40 · 20 AUG14:09 · 20 AUG14:39 · 20 AUG

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