A CCTP transfer time is mostly the wait for Circle's attestation: the period between burning USDC on the source chain and Circle signing the message that lets the destination mint. Circle publishes average attestation times per source chain for two modes. Fast Transfer attests once a transaction is in a block, about 20 seconds from Ethereum and about 8 seconds from most rollups; Standard Transfer waits for hard finality, about 15 to 19 minutes from Ethereum (Circle finality and block confirmations). This page reorganizes that table for route planning.
​

Last reviewed: Nov 2026. Every time below is Circle's published average, not a measurement made for this page.
​

CCTP timing depends on the source chain, not the destination, because Circle signs only after the burn reaches the required confirmation level on the source. Fast Transfer needs a block confirmation and is subject to a global allowance; Standard Transfer needs hard finality. Destination minting adds one more transaction after the attestation is available.
​

Circle's documentation describes Fast attestations as "typically in seconds" and Standard attestations as "typically in minutes," and notes that some chains disable Fast Transfer as a source because Standard is already fast (Circle finality).
​

Fast Transfer matters most on chains whose hard finality is slow, mainly Ethereum and the optimistic and zero-knowledge rollups that inherit Ethereum finality. Circle lists fifteen source chains with Fast attestation averages. Solana is the outlier at under a second.
​

Fast Transfers carry a fee that varies by route and is retrieved from Circle's fee API; Standard Transfers of USDC are free at the protocol level (Circle CCTP fees).
​

Standard attestation times split into two groups. Chains with their own fast finality attest in seconds. Rollups that settle to Ethereum wait about 65 Ethereum blocks, so their Standard times look like Ethereum's. A few chains take hours, which is the main reason to prefer Fast or a different route from them.
​

Circle's chain table lists Fast Transfer as not applicable as a source for chains such as Polygon PoS, Avalanche and Sonic, because their Standard times are already short (Circle CCTP supported blockchains).
​

Attestation time is one input. A route planner also weighs the Fast fee, the Fast allowance, destination gas and whether anyone will submit the mint. For transfers that start on an Ethereum-finality chain, the choice is usually between paying for Fast, waiting for Standard, or using a routing layer that pays out first.

Worked corridor pages apply these times to specific pairs. To follow a transfer while it waits, see CCTP explorer.
​

Circle publishes a status page with component-level uptime. It is a record of past availability, not a guarantee, but it is the only public operational signal for CCTP and is worth checking before a large transfer.
​

On November 11, 2026, Circle's status page showed 90-day uptime of 98.99% for the Cross-Chain Transfer Protocol group and 100% for the Attestation Service component, with recent incidents listed for USDC on X Layer, Injective and Noble (Circle status).
​

These are Circle's averages. Network congestion, reorganization risk and the Fast Transfer allowance can push real transfers past them, and Circle can change confirmation requirements at any time. The page also omits destination-side gas and mint submission, which vary by setup.

The grouped table above is easier to scan, but route planners usually need one chain at a time. This table lists every mainnet source chain in Circle's Standard Transfer table with its block confirmation requirement and average attestation time, in the order Circle publishes it.
​

Circle defines the two modes by a minFinalityThreshold parameter on the burn: 1000 or lower requests Fast Transfer, and 2000 or higher requests Standard Transfer (Circle).
​

Rollups that settle to Ethereum cannot be final before Ethereum is. Circle waits for the Ethereum block that contains the rollup's batch to finalize, so Standard times on those chains track batch posting plus Ethereum finality, not the rollup's own block time. Three cases stand out.

Solana follows a different model. For Fast Transfer, Circle waits for a block to be confirmed by validators representing over two thirds of stake, about 2 to 3 blocks; for Standard, it waits for 32 blocks, about 17 seconds (Circle).
​

Every CCTP chain has a Circle-issued domain number, used when calling CCTP contracts and API endpoints, that does not match the chain's public chain ID. Circle's table also shows which chains can be a Fast source, which accept upfront fee payment on the source, and which can be a Forwarding Service destination.
​

Upfront fees let the sender pay Fast Transfer and Forwarding Service fees on the source chain instead of having them deducted at mint, and they apply to USDC only (Circle). On Stellar, Circle notes that USDC precision and address encoding differ, and directs inbound transfers through a forwarder contract so funds reach the right recipient (Circle).
​

These answers cover the questions most often asked about CCTP timing.
​

About 20 seconds for a Fast attestation or about 15 to 19 minutes for Standard, per Circle (Circle finality).
​

Base inherits Ethereum finality, so Standard waits about 65 Ethereum blocks (Circle finality).
​

No. Tron is not in Circle's CCTP chain table (Circle supported chains).
​

A Circle-issued number for each chain where CCTP contracts are deployed, for example 0 for Ethereum, 5 for Solana and 6 for Base. It is not the chain's public chain ID (Circle).
​

Circle cites Linea's longer finality period, which puts Standard attestations at about 6 to 32 hours. Linea is a Fast source, with about 8 seconds (Circle).
​

All times are copied from Circle's documentation fetched on November 11, 2026 and grouped for readability. No transfers were timed.