Bitstamp REST · ping degradation, 5 min on 23 SEP 2026
Bitstamp REST · ping — 33% of checks failing over the last minute (timeout) — from every region — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Bitstamp's public API on 23 SEP 2026 04:18 UTC. It lasted 5 min and ended 23 SEP 2026 04:23 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, timeout.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
- Bitstamp published its own notice.
- Bitstamp marked its notice resolved.
HOW IT FAILED
Over the window, 19 of 2,336 checks failed: timeout ×10, bad_body ×9.
REST latency for the failing endpoint, per minute, from 23 SEP 2026 03:48 UTC to 23 SEP 2026 04:53 UTC. The gap in the line is where nothing answered.
DID BITSTAMP SAY SO?
Bitstamp acknowledged the same event 4h 38m after up24 opened this incident, on 23 SEP 2026 08:56 UTC: “ATOM Deposits and Withdrawals Suspended”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
ATOM Deposits and Withdrawals Suspended · 23 SEP 2026 08:56 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.