Bitstamp REST · depth degradation, 5 min on 21 AUG 2026
Bitstamp REST · depth — p95 1262ms over five minutes, 4.9× the 7-day baseline of 255ms. up24 opened this incident from its own measurements of Bitstamp's public API on 21 AUG 2026 12:07 UTC. It lasted 5 min and ended 21 AUG 2026 12:12 UTC, when the component started answering again.
WHAT HAPPENED
- Bitstamp published its own notice.
- 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.
- Bitstamp marked its notice resolved.
HOW IT FAILED
Over the window, 0 of 780 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 21 AUG 2026 11:37 UTC to 21 AUG 2026 12:42 UTC. The gap in the line is where nothing answered.
DID BITSTAMP SAY SO?
Bitstamp acknowledged the same event 1h 01m before up24 opened this incident, on 21 AUG 2026 11:06 UTC: “Issues with ETH, BASE, SOL, BNB, TAO, HYPE, SUI, XPL, XTZ, ADA, FLR, TRX, ARB, OP withdrawals”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Issues with ETH, BASE, SOL, BNB, TAO, HYPE, SUI, XPL, XTZ, ADA, FLR, TRX, ARB, OP withdrawals · 21 AUG 2026 11:06 UTC
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 — 4 recorded transitions — and nothing on it is reported by Bitstamp.