Bitfinex WS · connection degradation, 2 min on 14 OCT 2026
Bitfinex WS — 6.7% of windows failing over the last five minutes (conn) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Bitfinex's public API on 14 OCT 2026 09:45 UTC. It lasted 2 min and ended 14 OCT 2026 09:48 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, conn.
- 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, 12 of 2,256 ten-second windows failed: conn ×12.
A stream has no latency of its own — a feed either delivers or it does not — so this is Bitfinex's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.
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 63 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.