Coinbase went down as bitcoin crossed $10,000

Coinbase experienced an outage on June 1, 2020, as bitcoin crossed $10,000 and a surge of customer traffic overwhelmed parts of the cryptocurrency exchange’s infrastructure.

The failure affected Coinbase’s website, its professional trading interface and mobile applications at a moment when customers were responding to a closely watched market threshold. Coinbase’s incident record placed the connectivity problems between 16:14 and 16:58 Pacific Daylight Time. The company’s later technical account said trading through its application programming interface remained functional, meaning the disruption was serious but not a complete halt to every route into the exchange.

That distinction mattered. Automated and institutional users with API access could continue submitting trades, according to Coinbase, while customers relying on web and mobile interfaces encountered errors. The incident therefore exposed an uneven form of market access during a volatile period rather than a shutdown of Bitcoin or the broader cryptocurrency market.

A market move became an infrastructure test

Coinbase subsequently recorded bitcoin reaching $10,000 at approximately 16:05 PDT on June 1. The company did not identify a consolidated index, exact execution venue or individual trade behind that figure, so it should be read as Coinbase’s contemporaneous price observation rather than a universal bitcoin fixing.

Bitcoin trades continuously across multiple exchanges, and prices can differ between venues. There is no shared closing auction equivalent to those used in many securities markets. This reconstruction therefore makes no claim about a universal June 1 close, daily return or trading volume. It also does not assert that the Coinbase outage caused bitcoin’s price to rise or fall.

The defensible connection was operational: Coinbase said the rising market coincided with traffic increasing fivefold in four minutes. Its automatic capacity-scaling system could not expand quickly enough. Internal-service latency increased, and the web servers handling incoming requests became saturated because requests exceeded the available listening processes.

For customers, that translated into queued requests, timeouts and immediate failures. Coinbase reported that its request-error rate reached 50%. That percentage was the company’s internal measurement during the incident, not an independent audit or an estimate that half of all cryptocurrency trades worldwide failed.

Why the outage mattered

The breakdown illustrated a persistent contradiction in cryptocurrency markets. Bitcoin’s network continued processing blocks without dependence on Coinbase, but many people reached the market through centralized companies whose websites, applications and account systems could fail under load.

Crossing $10,000 also carried unusual visibility. Round-number price thresholds can prompt customers to check balances, place orders or open applications simultaneously. Coinbase’s account connected that behavior to the abrupt traffic increase, but it did not establish how many individual customers attempted to trade, how many orders failed or what financial effect the interruption had on users.

Contemporaneous reporting treated the timing as especially significant because access deteriorated during a sharp market move—the period when customers most expected an exchange to remain available. The surviving evidence does not support claims that Coinbase deliberately restricted trading or that the underlying Bitcoin network malfunctioned.

Later technical clarification

Coinbase published its postmortem on June 5, 2020. It said an overloaded health-check process caused some saturated servers to be classified as unhealthy and removed from the load balancer, worsening the shortage of available capacity. Engineers redeployed the service at 16:20 PDT to add machines, but the transition produced another two-minute outage when replacement instances also saturated.

By June 5, Coinbase said it had changed the health endpoint so saturated instances would not be removed in the same manner. It also identified pre-scaling, caching and deployment-process improvements as continuing work.

That later account clarifies the June 1 failure without changing what the event established: a prominent centralized gateway could remain technically connected to cryptocurrency markets through its trading API while its customer-facing access routes degraded at a critical moment. The incident was an infrastructure warning, not a failure of Bitcoin’s protocol.