Coinbase resolves September 3 Ethereum send and receive delays
Coinbase recorded a temporary delay affecting some Ethereum sends and receives on September 3; the exchange said trading, fiat rails and customer funds were unaffected.
This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.
On September 3 at 04:07 Pacific, Coinbase opened an incident titled “Delayed Sends and Receives - Ethereum Network” (incident 22975yrx3lqn). At 05:25 Pacific, roughly 78 minutes later, it marked the incident resolved. The status page entry carried an impact rating of none, and the public update text said only this: “Some users may experience delayed sends and receives on the Ethereum network. Buys, Sells, and Fiat withdrawals/deposits remain unaffected. We’re working on this issue and will provide updates as soon as possible. Your funds are safe.”
That is the entire official record. There is no post-mortem, no root cause, and no count of affected users.
What the three updates actually show
The incident moved through three states, and the gaps between them are the informative part:
- 04:07 — investigating. The message above is the opening notice.
- 04:58 — monitoring: “A fix has been implemented and we are monitoring the results.”
- 05:25 — resolved: “This incident has been resolved.”
Roughly 51 minutes passed before a fix was in place, and monitoring ran for another 27 minutes before the all-clear. Coinbase did not publish a post-mortem at any point, so “a fix has been implemented” is the only causal detail available to an outside reader.
This was the second Ethereum delay in two days
The same status page shows a separate incident, 5ggw7yq79mh4, opened on September 2 at 14:57 Pacific and resolved at 17:08 — about 131 minutes, using near-identical wording. Two consecutive days, two Ethereum send-and-receive delays on the same venue.
That pattern matters more than either incident alone. A single delay is ordinary infrastructure noise. Two in two days, with no disclosed common cause, is the kind of recurrence that should shape how you treat a pending withdrawal.
What the wider status history looks like
Across the 50 incidents Coinbase’s public status API currently exposes (August 22 through October 8), 33 carry an impact rating of none and 17 are rated minor. None is rated critical or major. Of the 49 that are resolved, the median time to resolution is about 81 minutes, but the distribution is long-tailed: the slowest ran past 9,600 minutes, and the 90th percentile sits above 4,300 minutes.
In plain terms: most Coinbase incidents are short and small, and a minority sit open for days. Both facts matter when you are staring at a transfer that has not confirmed.
What a delayed send does and does not mean for your funds
A delay in Coinbase’s send pipeline is a queue and settlement problem, not a transfer of ownership. The coins have not left your account until the transaction is broadcast and confirmed on chain. The practical consequence is that the transaction may still be in flight rather than lost.
The real risk here is not the delay. It is the retry. If you re-send because the first transfer looks stuck, you can end up with two outbound transactions, and the second one spends gas a second time and can settle later than you expect. Before you do anything:
- Open the transaction in a block explorer and confirm it exists and is included. Absence of a hash after a reasonable window is a different problem from a hash with no confirmation yet.
- Compare the pending entry against your Coinbase transaction history rather than against a screenshot of the app.
- Note the time the incident was resolved. Transfers queued during a resolved incident generally clear without action.
- Treat “your funds are safe” as a statement about custody, not about timing. It says nothing about when the transfer will settle.
What this record does not tell you
Coinbase disclosed no root cause, no affected-user count, and no confirmation that pending transactions were prioritized or delayed differently across accounts. The impact rating of none refers to the incident’s severity classification on the status page, not to a guarantee that any individual transfer completed on time. If your own transaction is still unresolved, the status page will not tell you why — only your support case will.
Source: Coinbase Status, incident 22975yrx3lqn, opened 2026-09-03T04:07:44 Pacific and resolved 2026-09-03T05:25:52 Pacific. Comparison incident 5ggw7yq79mh4 opened 2026-09-02. History figures come from the public status API on the editorial check date below.
-
Coinbase Status: https://coinbase.statuspage.io/
-
Incident permalink: https://stspg.io/2whd22bdmmn3
-
Editorial source check time: 2026-10-09T03:20:00Z
This information is educational and is not financial, legal, or tax advice.