← Coinbase status page

Coinbase REST · ticker outage, 4 min on 16 AUG 2026

Coinbase REST · ticker — 25% of checks failing over the last minute (timeout). up24 opened this incident from its own measurements of Coinbase's public API on 16 AUG 2026 12:42 UTC. It lasted 4 min and ended 16 AUG 2026 12:46 UTC, when the component started answering again.

OUTAGEREST · ticker · https://api.coinbase.com/api/v3/brokerage/market/products/BTC-USD
DURATION
4 min
STARTED
16 AUG 2026 12:42 UTC
ENDED
16 AUG 2026 12:46 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 16 AUG 2026 12:42 UTC
    up24 opened the incident at outage, timeout.
  2. 16 AUG 2026 12:46 UTC
    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, 4 of 762 checks failed: timeout ×4.

— p50‑ ‑ p95
axis 0 – 1000ms
12:13 · 16 AUG12:44 · 16 AUG13:16 · 16 AUG

REST latency for the failing endpoint, per minute, from 16 AUG 2026 12:12 UTC to 16 AUG 2026 13:16 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 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 — 2 recorded transitions — and nothing on it is reported by Coinbase.