Bitfinex REST · ticker degradation, 50s on 22 OCT 2026
Bitfinex REST · ticker — p95 602ms over the last five minutes, 7.7× the 7-day baseline of 78ms — from Carlstadt, US and Lauterbourg, FR. up24 opened this incident from its own measurements of Bitfinex's public API on 22 OCT 2026 16:25 UTC. It lasted 50s and ended 22 OCT 2026 16:25 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- 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 2,160 checks failed: timeout ×3.
REST latency for the failing endpoint, per minute, from 22 OCT 2026 15:55 UTC to 22 OCT 2026 16:55 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 67 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.