Coinbase outage on February 12, 2026: Buy, sell, and transfer functions unavailable for several hours.

On February 15, 2026, user funds were not compromised.On February 12, 2026, Coinbase experienced an outage that disrupted core platform functions for several hours, including buying, selling, transferring, and conversions. Some users were unable to trade during a period when the Bitcoin market was recovering after weeks of correction.The platform confirmed the incident through its status page, classifying it as a transaction and conversion issue, and reported its resolution later that day. There were no official public statements or press releases; communication was limited to technical monitoring channels.

Coinbase Outage on February 12: A Timeline of the Incident

According to the Coinbase Exchange status page, the outage affected core platform functions in the afternoon of February 12. The incident was reported, updated progressively, and then closed with a resolution notice. Coinbase did not provide a public technical analysis of the root cause.The affected functions included:

Spot buying and selling — impossible to place or execute orders
Conversions — blocked for the duration of the outage
Transfers to external wallets — suspended or resulting in errors

User funds were not at risk during any phase of the incident, as confirmed by the exchange.

The Timing Was Unfortunate

On February 12, the crypto markets were experiencing a rebound after a period of weakness in the preceding weeks. Trading volumes were above average, and volatility was present. Being locked out of an exchange during this period has direct and tangible consequences: you cannot reduce exposure if the market turns against you, you cannot close losing positions, and you cannot react to sudden news.In a market that operates 24 hours a day, seven days a week, a service interruption during periods of high activity is not just a technical inconvenience—it is an operational risk that directly impacts your portfolio.

Coinbase’s Response: Only the Status Page

The official communication was minimal: technical updates on the status page, no significant posts on official social media channels, and no press releases. Those actively monitoring the status channels had access to information in near real-time. Others discovered the issue only when attempting to use the platform and finding it unavailable.This pattern is repeated in large centralized exchanges: operational transparency exists, but it is passive. It requires the user to know where to look for it, rather than being proactively provided with the information.

Not an Isolated Incident: The Structural Problem of CEX Exchanges

Coinbase has experienced outages in the past, often coinciding with periods of high volatility—events such as Bitcoin halvings, sudden flash crashes, or significant macroeconomic announcements have historically put stress on the infrastructure of centralized exchanges across the industry.The question to ask is not whether it will happen again (almost certainly it will), but what factors are truly important to a user:

Frequency: how often does the exchange experience incidents that impact operability
Duration: how long does it take to resolve an incident
Scope: which functions are blocked (only deposits, or also trading and withdrawals)
Communication: does the platform provide real-time updates or disappear into silence

These parameters, not what happens under normal conditions, are what truly measure the reliability of an exchange.

What to Do After a Coinbase Outage: Managing Concentration Risk

The outage of February 12 highlights a risk that is often underestimated: concentrating all operations on a single exchange is a concentration risk, just like having an undiversified portfolio.Some practical steps to reduce exposure to this type of disruption include:

Distributed operations across multiple exchanges. Having active and verified accounts on two or three platforms allows for quick transfers if one is down. It is not necessary to distribute all funds; it is enough to have the alternative already operational, not to be activated in an emergency.
Separate trading and custody. Keeping assets in self-custody that are not actively being traded reduces dependence on the uptime of the exchange. Funds that are not being actively traded do not need to be on a centralized platform.
Do not operate close to fixed deadlines. Planning operations with sufficient lead time avoids being forced to act exactly when the service is unavailable.

In Summary

Aspect	Detail
Incident Date	February 15, 2026
Duration	Several hours (resolved within the day)
Blocked Functions	Buying, selling, transferring, conversions
Compromised Funds	No
Official Communication	Only status page, no announcements