Coinbase REST · ticker degradation, 50s on 20 OCT 2026
Coinbase REST · ticker — 25% 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 Coinbase's public API on 20 OCT 2026 04:11 UTC. It lasted 50s and ended 20 OCT 2026 04:11 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.
HOW IT FAILED
Over the window, 11 of 2,157 checks failed: timeout ×11.
REST latency for the failing endpoint, per minute, from 20 OCT 2026 03:41 UTC to 20 OCT 2026 04:41 UTC. The gap in the line is where nothing answered.
DID COINBASE SAY SO?
Coinbase 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 23 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 — 2 recorded transitions — and nothing on it is reported by Coinbase.