Coinbase REST · depth degradation, 50s on 17 NOV 2026
Coinbase REST · depth — 25% of checks failing over the last minute (timeout) — from Singapore, SG and Lauterbourg, FR — 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 17 NOV 2026 19:14 UTC. It lasted 50s and ended 17 NOV 2026 19:15 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, 10 of 2,196 checks failed: timeout ×10.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 17 NOV 2026 18:44 UTC to 17 NOV 2026 19:45 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 22 incidents for Coinbase in the last 90 days; 7 line up with something Coinbase published within six hours, and the rest have no published report near them. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so none of it should be read as a scoop . 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.