A network-specific Coinbase Payments disruption
Coinbase has marked a disruption affecting USDC payments on Polygon as resolved. In its initial status update, the company said some users were experiencing problems completing payments through Coinbase Payments when Polygon was the selected network.
The notice narrowed the reported impact to that payment route. Coinbase said payments using other networks, including Base and Ethereum, were not affected, and it told users their funds were safe. The status page did not report a broader Coinbase exchange outage or a problem with USDC reserves.
Timeline of the incident
Coinbase opened the incident on August 22 at 04:31 PDT. On August 24 at 10:56 PDT, the company posted identified, monitoring, and resolved updates, stating that it had found the issue, implemented a fix, and completed monitoring.
Because those later status changes carry the same displayed minute, the public incident record does not provide a more precise sequence for the fix and recovery. It also does not identify the technical root cause or quantify how many users or payments were affected.
What the status notice does—and does not—show
A payment route combines several systems: Coinbase's payment service, network-specific transaction handling, wallet and address logic, and the underlying blockchain. A problem limited to one route should not automatically be described as a Polygon network outage or a USDC failure without evidence from those systems.
The strongest supported conclusion is narrower: Coinbase Payments experienced degraded functionality for some USDC payments on Polygon, while the company reported Base and Ethereum routes as unaffected. The incident page confirms recovery but leaves the underlying cause undisclosed.
What users should verify after an incident
Anyone with a payment submitted during the affected window should check the transaction state in Coinbase and on the relevant block explorer before retrying. Repeating a payment without checking can create duplicate-intent or reconciliation problems even when only one transaction ultimately settles.
For merchants and developers, the incident is a reminder to expose network-specific status, preserve transaction identifiers, and design retry behavior around confirmed state rather than a generic success or failure message. Coinbase's current status page is the authoritative place to check for any recurrence.
Primary sources
CryptoDigest reviewed the following records when reporting this article. Source links are provided so readers can verify the underlying facts directly.
- Coinbase status incident report ↗Primary incident timeline and Coinbase's description of affected and unaffected payment routes.
See our editorial policy for sourcing, corrections, and conflicts standards.