Live check
Is Coinbase down right now?
Observed from Coinbase’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the Coinbase incident checklist
- Scope the surface. Coinbase's status page separates the consumer app, Advanced Trade, the Exchange, the API and sign-in. An API incident and a website incident call for very different responses — check which component the status page names.
- Read the error class before retrying. For integrations, 429 means rate-limited and 5xx/timeouts mean service trouble. Back off with exponential delay and jitter; a tight retry loop against a degraded API amplifies their outage into yours and burns your rate limit.
- Don't blind-retry money movements. Re-submitting a withdrawal, transfer or order that may have been accepted risks duplicate intent. Prefer idempotent requests and verify the actual state through the API or account after recovery rather than firing again.
- Distrust stale market data. If price or account feeds lag during an incident, any automation acting on them is acting on stale numbers. Pause trading bots and alerts keyed off Coinbase data until the feed is confirmed current.
- Expect sign-in and 2FA friction. New logins and 2FA can fail while existing sessions persist. Don't assume a failed login means an account problem during a platform incident.
What breaks when Coinbase has issues
A Coinbase incident lands differently depending on the component: trades and orders can be delayed or rejected, deposits and withdrawals can queue, API integrations fail or get rate-limited, market-data feeds go stale, and sign-in/2FA can block new sessions. The dangerous move during an incident is retrying money movements blindly — verify state after recovery instead. A status incident reflects platform availability; for anything about your specific account or balances, rely on Coinbase's official incident updates and support, not third-party pages.
FAQ
Is it Coinbase or my connection?
Check status.coinbase.com for the component you're using (consumer, Advanced Trade, Exchange, API, sign-in). If it's green, test your own network and try another site before assuming a platform outage.
Should I keep retrying a stuck order or withdrawal?
No. Re-submitting risks a duplicate once service recovers. Use idempotent requests where possible and verify the actual state through your account or the API after the incident clears rather than firing again.
Is the API down, or am I just rate-limited?
Distinguish 429 (rate limiting — back off) from 5xx/timeouts (service trouble). The status page's API component tells you which; tune retries with exponential backoff and jitter either way.
Where does Coinbase post official updates?
On status.coinbase.com, per component with an incident timeline — the same public page this widget reads. For account-specific questions, use Coinbase's official support and communications, not third-party trackers.
Put Coinbase’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches Coinbase and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with Coinbase. Status data comes from their public status page.