Coinbase REST · ping degradation, 2 min on 22 OCT 2026
Coinbase REST · ping — p95 645ms over the last five minutes, 4.4× the 7-day baseline of 146ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Coinbase's public API on 22 OCT 2026 16:03 UTC. It lasted 2 min and ended 22 OCT 2026 16:05 UTC, when the component started answering again.
WHAT HAPPENED
- Coinbase 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.
HOW IT FAILED
Over the window, 1 of 2,241 checks failed: timeout ×1.
REST latency for the failing endpoint, per minute, from 22 OCT 2026 15:33 UTC to 22 OCT 2026 16:35 UTC. The gap in the line is where nothing answered.
DID COINBASE SAY SO?
Coinbase acknowledged the same event 1h 00m before up24 opened this incident, on 22 OCT 2026 15:02 UTC: “Card Payment Unavailable (US) - Try Another”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Card Payment Unavailable (US) - Try Another · 22 OCT 2026 15:02 UTC
up24 opened 25 incidents for Coinbase in the last 90 days; 11 fall within six hours of something Coinbase published, and the rest were never mentioned. At the median, Coinbase's own notice came 1h 00m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 4 that up24 timestamped first are not scoops. Every entry links to the venue's own notice so the pairing can be judged.
COINBASE — OTHER INCIDENTS
Measured by up24's own probe against Coinbase's public API, BTC-USD against USD, every 5s. This page is generated from the incident's own rows — 3 recorded transitions — and nothing on it is reported by Coinbase.