Coinbase outage disrupted access as bitcoin approached $17,000

Coinbase’s web and mobile applications suffered an extended outage on November 16, 2020, interrupting customer access while bitcoin was climbing toward $17,000. The incident exposed a familiar tension in cryptocurrency markets: a decentralized asset can continue trading globally even when a major centralized gateway becomes unavailable.

Coinbase later documented that production traffic began dropping sharply at approximately 3:32 p.m. Eastern Standard Time. Its incident-response process was active by 3:38 p.m., and engineers began rolling back a change associated with an internal security-certificate migration. Nearly every service had recovered by approximately 5:04 p.m.

Measured from the first observed traffic collapse to near-complete recovery, the disruption lasted about 92 minutes. That duration is a calculation from Coinbase’s reported timestamps, not a company-provided measure of uniform downtime. Individual services and customers may have experienced shorter or different periods of unavailability.

A failure at the access layer

Coinbase attributed the initial breakdown to a Transport Layer Security certificate applied to an external load balancer where it did not belong. Internal services expected a different certificate chain and could no longer validate connections correctly, producing a cascade of service interruptions.

The attempted recovery created a second complication. Services being redeployed encountered what Coinbase described as a “thundering herd” problem: many requests returned at once while critical infrastructure was restarting. Engineers temporarily blocked traffic to one core backend service, increased its machine capacity and then restored connectivity as the redeployment stabilized.

The distinction matters. The incident was not evidence that the Bitcoin network had stopped processing blocks or that the broader bitcoin market had closed. It was a failure inside a centralized company whose applications provided account access and transaction services. The available record does not quantify how many customers were affected, how many orders could not be submitted or whether any attempted trades received materially different execution after service returned.

Bitcoin’s rally supplied the market pressure

The outage coincided with a fast-moving session. CoinDesk’s contemporaneous market wrap placed bitcoin at approximately $16,829 at 21:00 UTC on November 16, up 6.1% over the preceding 24 hours, using its bitcoin price index. It reported a 24-hour range of $15,792 to $16,851. Those figures describe an index and rolling measurement window; they are not the opening, high, low and close of a single exchange.

CoinMarketCap’s historical snapshot separately recorded bitcoin at $16,712.21 with a 4.74% 24-hour gain. Differences between the figures reflect snapshot timing, venue coverage and aggregation methodology. They should not be treated as contradictory exchange closes.

The move followed bitcoin’s first break above $16,000 since January 2018. Coinbase’s own November 14 market update had reported rising participation from both new and existing institutional buyers during the preceding week. That company commentary was directional rather than a complete, independently audited flow dataset, so it cannot establish how much institutional demand caused the November 16 advance.

Why the outage mattered

For customers, the immediate issue was access during volatility. A market participant unable to load an application may be unable to review balances, submit an order or respond to a rapid price change. For the industry, the outage demonstrated that operational resilience at exchanges remained distinct from the resilience of the underlying protocol.

Coinbase said on November 18 that it had begun scanning more than 700 load balancers for configuration mismatches and had automated certificate-change filtering to exclude external load balancers. Those measures were reported after the event and describe the company’s planned remediation; they do not prove that every related failure mode had already been eliminated on November 16.