Bitstamp REST · depth degradation, 3 min on 09 OCT 2026
Bitstamp REST · depth — p95 3140ms over the last five minutes, 4.7× the 7-day baseline of 671ms — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Bitstamp's public API on 09 OCT 2026 14:43 UTC. It lasted 3 min and ended 09 OCT 2026 14:46 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, 2 of 1,929 checks failed: bad_body ×2.
REST latency for the failing endpoint, per minute, from 09 OCT 2026 14:13 UTC to 09 OCT 2026 15:16 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 189 incidents for Bitstamp in the last 90 days; 7 fall within six hours of something Bitstamp published, and the rest were never mentioned. At the median, Bitstamp's own notice came 1h 34m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 2 that up24 timestamped first are not scoops. 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.