Coinbase REST · ticker degradation, 20s on 01 SEP 2026
Coinbase REST · ticker — 50% of checks failing over the last five minutes (timeout) — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Coinbase's public API on 01 SEP 2026 21:23 UTC. It lasted 20s and ended 01 SEP 2026 21: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.
- Coinbase published its own notice.
- Coinbase marked its notice resolved.
HOW IT FAILED
Over the window, 35 of 2,089 checks failed: timeout ×35.
REST latency for the failing endpoint, per minute, from 01 SEP 2026 20:53 UTC to 01 SEP 2026 21:53 UTC. The gap in the line is where nothing answered.
DID COINBASE SAY SO?
Coinbase acknowledged the same event 3h 32m after up24 opened this incident, on 02 SEP 2026 00:55 UTC: “Degraded performance - Coinbase Onramp”. 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 · 02 SEP 2026 00:55 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.