Coinbase briefly delayed Solana sends and receives late on 21 September, while trading and fiat rails stayed outside the incident. That makes the practical question narrower than a Solana outage: users needed to separate a Coinbase transfer queue from market access and from Solana’s own public network status.
| What you need to know |
|---|
| Coinbase reported delayed sends and receives on Solana at 18:28 PDT on 21 September 2026 and marked the incident resolved at 18:55 PDT. |
| The status notice said buys, sells and fiat withdrawals or deposits were not affected. |
| Solana's own status page listed all monitored systems operational and no incidents for 21 or 22 September. |
| The useful check for users was transfer timing, not a new claim about Solana network downtime or Coinbase trading access. |
What Coinbase actually reported
The Coinbase status page logged the Solana incident as a sends-and-receives delay, not as a trading halt. Its first update said some users could see delayed Solana sends and receives, while buys, sells and fiat withdrawals or deposits were not affected. Coinbase added that customer funds were safe, then moved the notice to identified and resolved at 18:55 PDT, about 27 minutes after the first timestamp.
For Dutch and European users, that timestamp matters because the notice landed in the early hours of 22 September CEST. A pending withdrawal during that window could have looked like a market problem if checked only from an account screen. The narrower reading is more useful: Coinbase was reporting a platform-side transfer delay for one network, not saying spot trading or euro funding had stopped.
Why Solana’s status page changes the reading
The separate Solana status page listed all monitored systems operational and showed no incident for 21 September or 22 September. That does not prove every individual transaction experience was smooth, and it does not explain Coinbase’s internal queue. It does keep the evidence in the right lane: this was a Coinbase-status incident around sends and receives, not confirmed public evidence of a Solana mainnet outage.
That distinction is also why this story should not be stretched into a broad exchange-risk claim. A user trying to move SOL or tokens on Solana needed to check Coinbase’s operational page before retrying, but a trader looking at buys and sells had a different risk question. Coinbase’s own notice explicitly carved out trading and fiat activity.
The checklist before moving funds
When a network-specific notice appears on an exchange status page, the first useful check is the exact product named in the incident. Sends and receives affect deposits and withdrawals. They do not automatically mean the order book is paused, a bank transfer is blocked or the underlying network is down.
The second check is whether an independent network-status page shows a matching incident. In this case, Solana’s page did not. That leaves a cautious but practical conclusion: users should wait for the exchange resolution notice before repeating a withdrawal, while avoiding the larger claim that Solana itself had a documented outage. The Coinbase incident was resolved, but the read-across for future alerts remains valuable.
This article is informational and not financial advice. Crypto-assets can lose value, and operational status pages may change after publication. Check the relevant platform notices before sending funds.
