Coinbase is working to restore normal Hedera transfers after some customers experienced delays sending and receiving HBAR, while trading and fiat services remain unaffected.
The cryptocurrency exchange first acknowledged the disruption at 10:04 p.m. PDT on Aug. 28, saying users could experience delayed HBAR sends and receives. Coinbase said HBAR buying and selling remained available and that fiat deposits and withdrawals were operating normally. It also told customers their funds were safe.
Just under two hours later, at 12:01 a.m. PDT on Aug. 29, Coinbase moved the incident from “Investigating” to “Identified,” saying it had found the issue and was implementing a fix. As of that update, the company had not disclosed the technical cause or provided an estimated time for full restoration.
The distinction is important for customers holding HBAR on Coinbase. The disruption does not prevent users from trading the asset inside the exchange, according to Coinbase. Instead, it affects blockchain transfers into and out of the platform, potentially leaving incoming HBAR deposits pending longer than normal or delaying customers trying to move HBAR from Coinbase to an external wallet.
Coinbase officially supports Hedera for both trading and custody, with its digital-asset disclosures listing HBAR as available for both trading and custody services.
Hedera’s native HBAR token is used to pay network transaction fees and secure the network through staking. Coinbase market data put HBAR at roughly $0.088 on Aug. 29, with a market capitalization of about $3.8 billion and approximately 43 billion tokens in circulating supply.
Hedera Upgrade Preceded Coinbase’s Transfer Problems
The Coinbase incident came several hours after scheduled maintenance on the Hedera mainnet, although neither company has said the two events are connected.
Hedera scheduled an upgrade of its mainnet to version 0.76 for 2:00 a.m. UTC on Aug. 29 and warned beforehand that users should expect some disruption to network services during a maintenance window expected to last approximately 40 minutes.
Hedera reported at 2:10 a.m. UTC that the scheduled work was in progress and, six minutes later, said the mainnet had been upgraded to version 0.76.3 and was available for use while the organization performed additional verification.
Coinbase did not announce its HBAR problem until approximately 5:04 a.m. UTC, around three hours after Hedera’s scheduled maintenance began.
That timing makes the network upgrade relevant context, but there is currently no evidence that it caused Coinbase’s transfer delays. Coinbase has not attributed the problem to Hedera, and Hedera did not report a network-wide incident on Aug. 28.
Hedera’s status page currently shows the mainnet itself as operational and reports 100% network uptime over the preceding 90 days. Individual-node status is less uniform: a node operated by IBM was listed as experiencing a partial outage, while a Dell-operated node has been undergoing previously scheduled maintenance running from Aug. 27 through Aug. 31. The network’s mirror-node services and APIs were shown as operational.
That suggests the Coinbase disruption could instead sit within the exchange’s own HBAR infrastructure — such as wallet processing, node connectivity, deposit detection or withdrawal broadcasting — although Coinbase has not identified the affected component publicly.
Coinbase Has Seen Several Network-Specific Delays This Month
The HBAR problem also follows several other short-lived asset or network disruptions on Coinbase during August.
On Aug. 14, the exchange reported delayed sends and receives on the Sui network. The incident was resolved about an hour later.
Coinbase then reported delayed Ethereum sends and receives on Aug. 17, followed by another Ethereum send delay on Aug. 20 and a further delayed-sends incident on Aug. 21. The Aug. 21 disruption occurred alongside a separate issue involving delayed ARBETH receives. In each case, Coinbase said trading and fiat deposits and withdrawals remained available.
Another incident beginning Aug. 22 affected some USDC payments over Polygon through Coinbase Payments. Coinbase identified and resolved that problem on Aug. 24 while payments using Base and Ethereum remained unaffected.
Those incidents involved different networks and products, and there is no evidence linking them technically to the current Hedera disruption. They do, however, illustrate the operational complexity exchanges face when supporting transfers across dozens of independent blockchain networks.
Analysis: An Operational Problem Can Exist Even When the Blockchain Is Working
The most useful detail in the Coinbase incident is what is still functioning.
Users can buy and sell HBAR. Fiat deposits and withdrawals are unaffected. Coinbase says customer funds remain safe. Meanwhile, Hedera’s mainnet is reporting itself operational.
That combination points toward an important distinction that crypto users sometimes miss: an exchange’s ability to move a token and the underlying blockchain’s ability to process transactions are not the same thing.
A centralized exchange does not simply press a button and place every withdrawal directly onto a blockchain.
It maintains wallet infrastructure, nodes or node providers, deposit-monitoring systems, transaction-signing systems, hot and cold wallet balances, confirmation requirements and internal risk controls. Problems anywhere in that chain can stop or slow deposits and withdrawals even while the underlying network continues producing transactions normally.
That is why an HBAR holder can see Hedera functioning elsewhere while waiting for Coinbase to credit a deposit.
The timing around Hedera’s v0.76.3 upgrade makes this incident more interesting. Exchanges frequently need to ensure their infrastructure remains compatible with blockchain upgrades, and scheduled network maintenance can temporarily affect transaction processing.
But timing alone is not enough to assign blame. Hedera made the upgraded network available shortly after 2:00 a.m. UTC, while Coinbase did not report its problem until several hours later. Without an explanation from Coinbase, saying the upgrade caused the delay would go beyond the available evidence.
The good signal for users is Coinbase’s transition from “Investigating” to “Identified.” Operationally, those status categories mean something different. The company is no longer publicly saying it is searching for the problem; it says it knows what the problem is and is implementing a remedy.
The less encouraging part is that no resolution has yet been posted.
For traders who simply hold or trade HBAR inside Coinbase, the practical effect should be limited as long as buying and selling remain available. The consequences are more significant for users who need to move tokens immediately — for example, to self-custody, another exchange, a staking setup or an application running on Hedera.
This is also why exchange status incidents should not automatically be interpreted as blockchain outages.
Hedera can be operational while Coinbase HBAR transfers are impaired, just as Coinbase itself can remain broadly operational while one network integration fails. The exchange’s website, mobile app, Advanced Trade, derivatives products and most digital currencies were all shown as operational while the HBAR-specific incident continued.
For now, the story remains an exchange-level transfer disruption rather than evidence of a wider Hedera failure. The next meaningful update will be whether Coinbase moves the incident into monitoring or resolved status — and, if it provides more detail, whether the timing of Hedera’s mainnet upgrade had anything to do with the problem.