Crypto exchanges have a cruel failure pattern: they go down exactly when you most need them — during a sharp market move — because that's when traffic spikes hardest. If Coinbase is frozen while the price is swinging, the first thing to establish is whether it's a real outage, a load-shedding throttle, or your own connection, because only one of those means "your order didn't go through."
Why exchanges go down when the market moves ¶
A volatility spike produces a flood of concurrent logins, price refreshes, and orders in a few minutes. Matching engines, databases, and the API tier all hit their limits at once. Exchanges respond by shedding load — showing maintenance pages, disabling trading temporarily, or rate-limiting — to protect the core ledger. That's deliberate self-defense, not the same thing as the whole platform crashing. The general mechanics are in the anatomy of an outage; exchanges just concentrate all of it into the worst possible five minutes.
The parts that fail separately ¶
- The website / app front-end — loading at all. Often fronted by a CDN, so a Cloudflare incident can break the front door without the exchange itself being down.
- The trading API + matching engine — placing and filling orders. This can be degraded (orders queue or reject) while charts still load.
- Deposits / withdrawals — often paused independently during incidents or chain congestion.
- Auth / 2FA — sign-in. A login outage locks you out even if trading is technically up.
The check ¶
- Probe from four regions. Check coinbase.com from US East, US West, Europe, and Asia. All four failing is a real outage; a mixed result is regional (or a CDN edge problem).
- Separate the exchange from the chain. "My withdrawal is stuck" is sometimes the exchange and sometimes on-chain congestion. The blockchain status hub checks whether the underlying chain is actually producing fresh blocks — an exchange can be perfectly up while the network it's trying to settle on is backed up.
- Read the status page for scope. Coinbase's own incident feed will say whether it's site-wide, trading-only, or deposits/withdrawals — which tells you whether your order is at risk or just the UI is slow.
Exchange down vs. chain congestion ¶
| Symptom | Likely cause | Where to look |
|---|---|---|
| Site won't load at all | Front-end / CDN outage | Multi-region probe + Cloudflare status |
| Orders reject or hang | API / matching engine overload | Coinbase status feed |
| Withdrawal pending forever | Chain congestion or paused withdrawals | Chain status + status feed |
| Can't log in | Auth / 2FA incident | Status feed; wait, don't retry-storm |
| Only you affected | Local / network | Different network, flush DNS |
What to do (and not do) during an exchange outage ¶
Don't retry-storm — repeatedly resubmitting an order during an incident risks duplicate fills once things recover, and it adds load that slows recovery for everyone. Confirm scope on the status feed before assuming your order failed; "the UI is frozen" and "my order didn't execute" are not the same thing, and many orders that appear stuck actually filled. If the exchange is genuinely down, there's no client-side fix — wait, and check your order history once it's back before re-trading.
FAQ ¶
Is Coinbase down for everyone or just me?
Probe coinbase.com from multiple regions. If all fail, it's a real outage; if all succeed but you can't reach it, it's your network. During volatility, also check the status feed for a partial incident — trading or withdrawals can be paused while the site itself loads fine.
Why does Coinbase always go down when the price moves?
Volatility drives a sudden flood of logins and orders that pushes the matching engine and API past their limits. Exchanges deliberately shed load — pausing trading, showing maintenance pages, or rate-limiting — to protect the core ledger. It's self-defense under peak load, which is exactly why it happens at the worst moment.
My withdrawal is stuck — is that Coinbase or the blockchain?
It can be either. Coinbase may have paused withdrawals during an incident, or the underlying chain may be congested and slow to confirm. Check both: the exchange's status feed for a withdrawal pause, and the chain status to see whether the network is producing fresh blocks. A chain that's "up but not advancing" delays settlement even when the exchange is fine.