← Bitstamp status page

Bitstamp WS · book degradation, 4 min on 18 NOV 2026

Bitstamp WS · book — 33% of windows stalled over the last minute (stalled) — from every region. up24 opened this incident from its own measurements of Bitstamp's public API on 18 NOV 2026 12:54 UTC. It lasted 4 min and ended 18 NOV 2026 12:58 UTC, when the component started answering again.

DEGRADEDWS · book · diff_order_book_btcusd
DURATION
4 min
STARTED
18 NOV 2026 12:54 UTC
ENDED
18 NOV 2026 12:58 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 18 NOV 2026 12:54 UTC
    up24 opened the incident at degraded, stalled.
  2. 18 NOV 2026 12:58 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, 6 of 1,167 ten-second windows failed: stalled ×6.

— p50‑ ‑ p95
axis 0 – 1000ms
12:25 · 18 NOV12:56 · 18 NOV13:28 · 18 NOV

A stream has no latency of its own — a feed either delivers or it does not — so this is Bitstamp's REST endpoints over the same window, per minute, as the median across them, measured from Lauterbourg, FR. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

DID BITSTAMP SAY SO?

Bitstamp 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 74 incidents for Bitstamp in the last 90 days; 3 line up with something Bitstamp published within six hours, and the rest have no published report near them. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so none of it should be read as a scoop . Every entry links to the venue's own notice so the pairing can be judged.

BITSTAMP — OTHER INCIDENTS

Measured by up24's own probe against Bitstamp's public API, btcusd against USD, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by Bitstamp.