CCTP USDC Transfer Timing by Mode and Source Chain
How long does a CCTP USDC transfer take? Standard takes about 13–19 minutes from Ethereum or its rollups; Fast settles in seconds for a fee.
The Tareom Editors5 min read

A Standard CCTP USDC transfer from Ethereum or its rollups takes roughly 13–19 minutes; Fast Transfer can settle in seconds for a fee. The main wait is Circle’s attestation: for Standard, Circle signs only after the source chain reaches the required finality.
- Ethereum finality: two epochs × 32 slots × 12 seconds, or about 12.8 minutes.
- Standard from Ethereum, Arbitrum or Base: roughly 13–19 minutes.
- Fast Transfer: seconds on eligible routes, with a fee.
If you are choosing a route in Jumper bridge, the CCTP transfer speed depends on whether the quote uses Standard or Fast and which chain your USDC starts on. Jumper bridge shows available bridge and swap routes, including options relevant to this timing question.
What happens during a Standard CCTP transfer?
Take USDC moving from Base to Arbitrum on Standard. CCTP first burns the USDC on Base. Circle then waits for the source transaction to reach the required finality and signs an attestation, a message confirming the burn. The destination step uses that attestation to mint USDC on Arbitrum.
Base is a rollup that settles to Ethereum. That means a Standard CCTP transfer leaving Base waits for Ethereum finality, rather than finishing as soon as the Base transaction appears. The same timing principle applies when USDC leaves Arbitrum: its Standard transfer waits for Ethereum finality too.
Ethereum divides time into 12-second slots, with 32 slots in an epoch. Finality takes two epochs, which works out to about 12.8 minutes. Circle’s attestation and the destination mint add time around that wait, so a practical estimate for Standard transfers from Ethereum and its rollups is about 13–19 minutes.
That estimate is for the protocol steps, not a guaranteed arrival deadline. The source transaction must be submitted, Circle must issue its attestation, and the destination mint must be completed. Those steps can take longer if the network is busy or the attestation is delayed.
Why Arbitrum and Base do not make Standard faster
A faster-feeling rollup transaction does not remove the Ethereum finality wait from Standard CCTP. The relevant clock is the source chain’s settlement finality, not simply how quickly the transaction first shows as confirmed in your wallet.
So if you send USDC from Base to Arbitrum using Standard, the transfer still waits for Base’s settlement to Ethereum. Sending from Arbitrum to Base also waits for Ethereum finality. Either route can therefore take about as long as leaving Ethereum directly.
This is useful when planning around a deadline. If your funds need to arrive within a few minutes, treat Standard from Ethereum, Arbitrum or Base as too slow for that plan. If you can allow roughly 13–19 minutes, Standard is the slower option to compare against a Fast quote.
Standard can finish sooner when the source chain reaches finality sooner. That is why transfer time depends on where your USDC starts, even if the destination is the same. For the Ethereum rollups in this example, however, Ethereum settlement remains the key wait.
When Fast Transfer is worth choosing
CCTP V2 Fast Transfer can provide an attestation after soft finality, an earlier confirmation level than full finality. Circle can then attest before the source transaction reaches full finality, allowing the destination mint to happen in seconds on supported routes.
Fast is not available on every source chain or route, and it charges a fee. A route aggregator such as Jumper bridge may quote either Standard or Fast, depending on what the route supports. Compare the quoted arrival time and fee before you confirm; route availability and estimates can vary.
For a Base-to-Arbitrum transfer, choose Fast if the route offers it and seconds matter enough to justify the fee. Choose Standard if you can wait around 13–19 minutes and prefer to avoid the Fast fee. The mode and source chain give you the practical timing estimate to plan with.
Frequently asked questions
What if the CCTP attestation never arrives?
Check the transfer status using the source transaction details. Until Circle issues the attestation, the destination mint cannot use it. Delays can extend the estimate; consult the route’s status information before starting another transfer.
Which chains support CCTP?
CCTP works across a set of supported networks, and availability can differ by transfer mode. Check that both your source and destination are supported for the route you intend to use.
Do I need destination gas to mint CCTP USDC?
A destination mint may require a transaction on the destination chain, which uses that network’s gas token. Check the route and wallet prompts for the gas needed to complete the transfer.
Can a burned CCTP transfer be cancelled?
After the source transaction burns the USDC, the transfer proceeds through attestation and destination minting. Check the transfer status and the service handling the route for available recovery steps; do not assume a burn can be reversed.