← Bitstamp status page

Bitstamp REST · depth degradation, 20s on 02 NOV 2026

Bitstamp REST · depth — p95 2428ms over the last five minutes, 4.3× the 7-day baseline of 562ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Bitstamp's public API on 02 NOV 2026 12:37 UTC. It lasted 20s and ended 02 NOV 2026 12:38 UTC, when the component started answering again.

DEGRADEDREST · depth · https://www.bitstamp.net/api/v2/order_book/btcusd/
DURATION
20s
STARTED
02 NOV 2026 12:37 UTC
ENDED
02 NOV 2026 12:38 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 02 NOV 2026 12:37 UTC
    up24 opened the incident at degraded.
  2. 02 NOV 2026 12:38 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 2,178 checks failed: timeout ×1.

— p50‑ ‑ p95
axis 0 – 10000ms
12:08 · 02 NOV12:38 · 02 NOV13:08 · 02 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 02 NOV 2026 12:07 UTC to 02 NOV 2026 13:08 UTC. The gap in the line is where nothing answered.

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.