Bridge speed is the gap between clicking "send" on chain A and your funds being spendable on chain B. In 2026, that gap ranges from 8 seconds on optimistic intent bridges to 19 minutes on canonical CCTP transfers, and the right answer depends entirely on which route you pick. This guide benchmarks the six most-used routes across the major bridge protocols, explains why finality models drive the numbers, and helps you choose the fastest route per destination.
​

Fastest means time from source-chain inclusion to destination-chain spendability, not just the source-chain confirmation. A bridge that confirms in 2 seconds but waits 15 minutes for finality before minting on the destination is not fast. The end-to-end clock is what users feel.
​

Three things gate that clock: source-chain finality requirements, the bridge's verification model (optimistic, intent-based, or canonical), and destination-chain block time. Intent bridges like Across short-circuit finality by fronting liquidity from a relayer; canonical bridges like CCTP wait for source finality before minting native USDC.
​

These numbers reflect median fill times observed across DeFiLlama bridge volume data and each protocol's published benchmarks for small-to-mid size transfers (under $50,000, where relayers fill instantly).

Two patterns jump out. First, intent-based bridges (Across, plus Hyperlane's warp routes) are an order of magnitude faster than canonical bridges because they front liquidity. Second, Ethereum-origin routes are slower than L2-origin routes because Ethereum mainnet has 12-second blocks and bridges often wait for multiple confirmations.
​

CCTP burns USDC on the source chain and mints native USDC on the destination, but the mint waits for source-chain finality (about 13 minutes on Ethereum, 8 minutes on Polygon). Across skips that wait by having a relayer pre-fund the destination and reconcile later. You get speed; the relayer takes finality risk and prices it into the fee.
​

This is the speed-versus-trust trade. Canonical bridges return native assets and inherit only Ethereum-level trust. Intent bridges return native assets too (Across fills with the canonical asset) but layer in a relayer assumption that gets unwound after L2-to-L1 finality. For most users moving under $50k, the trade is worth it.
​

Every bridge benchmark above is downstream of source-chain finality. Here is what each chain actually guarantees:

L2BEAT tracks these finality assumptions and the trust models behind every rollup, and is the canonical reference for which "soft" finality numbers you can rely on.
​

Relayers fill destination orders in seconds and reconcile with the canonical bridge later. Fastest for ETH and major stables on EVM L2s. Documented fill times are typically under 15 seconds for L2-to-L2 routes. Source: docs.across.to.
​

Unified liquidity pools with delta algorithm for rebalancing. Faster than canonical, slower than intent. Best for routes where you want a single pool of liquidity and finality-aware messaging. Source: stargateprotocol.gitbook.io.
​

General-purpose messaging layer. Token bridges built on LayerZero (USDT0, OFTs) inherit DVN-based verification times, typically 60-120 seconds end-to-end. Source: docs.layerzero.network.
​

Modular interchain security model with warp routes for token transfers. Faster on routes where validator sets are well-staffed. Eco partners with Hyperlane for cross-chain message delivery. Source: docs.hyperlane.xyz.
​

Burns USDC on source, attests via Circle, mints native USDC on destination. Slowest because it waits for source-chain finality, but returns native USDC every time with no liquidity risk. Source: developers.circle.com/stablecoins/cctp.
​

Relayer inventory exhaustion. Intent bridges are only fast while the relayer has destination liquidity. Large transfers can fall back to canonical-bridge speed without warning. Always check the bridge's quoted fill time before sending.
​

Source-chain congestion. Even a 10-second intent bridge becomes a 60-second bridge if the source chain has full blocks. Include source-chain inclusion time when budgeting.
​

Destination chain block time. A bridge that submits in 10 seconds still has to wait for the next destination block. Polygon's 2-second blocks and Solana's 400ms slots help; Ethereum's 12-second blocks hurt.
​

Eco Routes is an intent-based protocol that quotes execution across multiple underlying bridges (Hyperlane for messaging, CCTP for canonical USDC, plus integrations with major liquidity layers) and picks the fastest viable path for your transfer size. You submit one intent; solvers compete to fill it on the destination in seconds. Speed becomes the default, not a manual optimization.
​

Speed benchmarks were compiled from each bridge's public documentation (Across, Stargate, LayerZero, Hyperlane, Circle CCTP) and cross-referenced against DeFiLlama bridge volume data for May 2026. Finality numbers come from L2BEAT and each chain's spec. Numbers are medians for transfers under $50k, where relayer inventory is rarely a constraint. Larger transfers can fall back to canonical-bridge speed; always check the quoted fill time before sending.
​

Sources: docs.across.to, stargateprotocol.gitbook.io, docs.layerzero.network, docs.hyperlane.xyz, developers.circle.com/stablecoins/cctp, l2beat.com, defillama.com/bridges.
​