Coinbase monitors fix after Solana sends and receives were delayed

At 6:07 a.m. Pacific, Coinbase moved the incident to monitoring after implementing a fix. The company said customer funds were safe, but the incident was still listed as unresolved when this article was prepared. Monitoring is not resolution, and delayed transfers may continue while systems process backlogs.

The notice did not identify a root cause or say whether the delay originated in Coinbase infrastructure, a wallet service, transaction broadcasting or conditions on Solana itself. Without that detail, it would be premature to describe the event as a Solana network outage or a security breach.

Users should verify status before retrying

Repeatedly initiating transfers during a delay can create confusion once pending transactions begin moving. Customers should first check the transaction status and destination address, then use Coinbase's official support and status channels rather than responding to unsolicited messages offering to accelerate or recover funds.

A delayed send also differs from a failed or reversed transfer. Blockchain transactions may wait for broadcast, confirmation or exchange-side crediting, and the appropriate action depends on where the transaction is held. A status-page notice cannot establish the state of an individual account.

The next confirmation should be a formal resolved notice followed, ideally, by an explanation of cause and scope. Until then, the evidence supports a limited operational incident with trading and fiat functions available—not a claim that every Solana user or the underlying network was impaired.

Customers who need time-sensitive settlement should account for exchange processing risk even on fast blockchains. Self-custody may reduce dependence on an exchange's withdrawal system, but it introduces key-management, address and signing risks of its own; neither route is operationally risk-free.