Coinbase Commerce status history
Current state: operational — “All Systems Operational” per https://status.commerce.coinbase.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Coinbase Commerce incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: Partial Interruption — 129.9 days (2026-03-21 00:25 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (8)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-03-21 00:25 UTC | Partial Interruption | resolved | none | 129 d 20 h |
| 2026-02-07 21:37 UTC | Degraded Performance - Coinbase Commerce | resolved | none | 41 h 46 min |
| 2025-11-09 16:16 UTC | Commerce Payments | resolved | none | 1 h 05 min |
| 2025-10-20 07:33 UTC | Site Performance - Login, Trading, Transactions | resolved | minor | 17 h 25 min |
| 2025-10-15 14:07 UTC | Degraded performance - Coinbase Commerce | resolved | none | 23 h 27 min |
| 2025-09-26 07:23 UTC | Degraded performance - Coinbase Commerce | resolved | none | 37 h 51 min |
| 2025-09-18 01:12 UTC | Delayed Payment Confirmation | resolved | minor | 1 h 39 min |
| 2025-08-21 19:11 UTC | Degraded performance - Cloudflare Network Outage | resolved | none | 55 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Coinbase Commerce with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"coinbase-commerce"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
