Coinbase REST · depth degradation, 13 min on 14 AUG 2026
Coinbase REST · depth — p95 743ms over five minutes, 4.6× the 7-day baseline of 162ms. up24 opened this incident from its own measurements of Coinbase's public API on 14 AUG 2026 15:37 UTC. It lasted 13 min and ended 14 AUG 2026 15:50 UTC, when the component started answering again.
WHAT HAPPENED
- Coinbase published its own notice.
- Coinbase marked its notice resolved.
- 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, 5 of 875 checks failed: timeout ×5.
REST latency for the failing endpoint, per minute, from 14 AUG 2026 15:07 UTC to 14 AUG 2026 16:20 UTC. The gap in the line is where nothing answered.
DID COINBASE SAY SO?
Coinbase acknowledged the same event 2h 00m before up24 opened this incident, on 14 AUG 2026 13:37 UTC: “Degraded Performance - Coinbase Onramp Transactions”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Degraded Performance - Coinbase Onramp Transactions · 14 AUG 2026 13:37 UTC
up24 opened 20 incidents for Coinbase in the last 90 days; 9 fall within six hours of something Coinbase published, and the rest were never mentioned. At the median, Coinbase's own notice came 1h 47m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 3 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 — 4 recorded transitions — and nothing on it is reported by Coinbase.