← Coinbase status page

Coinbase REST · ticker degradation, 4 min on 18 NOV 2026

Coinbase REST · ticker — 33% 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 18 NOV 2026 18:30 UTC. It lasted 4 min and ended 18 NOV 2026 18:35 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://api.coinbase.com/api/v3/brokerage/market/products/BTC-USD
DURATION
4 min
STARTED
18 NOV 2026 18:30 UTC
ENDED
18 NOV 2026 18:35 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 18 NOV 2026 18:30 UTC
    up24 opened the incident at degraded, timeout.
  2. 18 NOV 2026 18:35 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, 11 of 2,340 checks failed: timeout ×11.

— p50‑ ‑ p95
axis 0 – 2000ms
18:01 · 18 NOV18:33 · 18 NOV19:05 · 18 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 18 NOV 2026 18:00 UTC to 18 NOV 2026 19:05 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.