Fastest cross-chain messaging protocol, live end-to-end delivery latency
Hyperlane leads cross-chain delivery at 27.06 s (p50, 24h) on Fastest cross-chain messaging protocol, live end-to-end delivery latency. End-to-end wall-clock delivery latency across the four cross-chain messaging protocols that expose source-tx-to-destination-execution data publicly (LayerZero, Chainlink CCIP, Hyperlane, Axelar), measured passively from each protocol's own tracker every 60 seconds.
TL;DR. As of , Hyperlane leads cross-chain delivery at 27.06 s (p50, 24h) on Fastest cross-chain messaging protocol, live end-to-end delivery latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/cross-chain-messaging-latency.
Cross-chain messaging is the plumbing under every serious bridge, cross-chain vault and interchain governance system. Four networks expose an end-to-end delivery signal on their public trackers: LayerZero, Chainlink CCIP, Hyperlane, Axelar. This bench compares their end-to-end delivery latency side-by-side on the same observation stack. Wormhole is measured separately (see wormhole-vaa-latency): its public tracker only exposes Guardian signing time, not destination-side execution, so it is not apples-to-apples with the four end-to-end signals here. Including it in this comparison would make Wormhole look 3x faster than it actually is at end-to-end delivery. Circle CCTP is on the roadmap: its Iris API does not expose a list-recent endpoint, so passive polling requires chain-scan on every CCTP source chain (5-7 days of build vs the 1-2 days each of the four benches here took). Every value on this page is a real user message; no canary transactions are sent. The p50/p90/p99 shown are aggregate across every corridor each protocol covers, over the last 24 hours.
Methodology
For each of the four cross-chain messaging protocols that expose source-tx-to-destination-execution timestamps publicly, we measure end-to-end delivery latency by polling that protocol's own message tracker every 60 seconds. Each observation is one delivered message. The p50/p90/p99 shown are aggregate across every corridor each protocol covers, over the last 24 hours. Data sources: scan.layerzero-api.com (LayerZero), api.ccip.chain.link (Chainlink CCIP), api.hyperlane.xyz (Hyperlane), api.axelarscan.io (Axelar).
Frequently asked
Why isn't Wormhole in this comparison?
Wormhole's public tracker (wormholescan) only exposes signing time, source-tx-to-Guardian-quorum. It does not consistently expose destination-side execution timestamps. Including Wormhole here would compare its signing time (about 18s aggregate) against LayerZero/CCIP/Hyperlane/Axelar end-to-end delivery (about 30s-20min) and make Wormhole look 3x faster than it actually is at delivery. Wormhole gets its own dedicated bench at wormhole-vaa-latency with correct signing-only methodology and full disclosure.
Why is Chainlink CCIP so much slower on Ethereum-source?
CCIP waits for source-chain finality before its DON commits a merkle root. On Ethereum, that means Casper FFG finalization (12-15 minutes typical, up to 25 minutes in adverse epochs). LayerZero and Hyperlane both sign pre-finality by default, so their end-to-end delivery excludes that wait. Axelar validators DO wait for source-chain confirmations on Ethereum (about 96 blocks, roughly 20 minutes), so Axelar shows a similar ETH-source slowdown, though smaller than CCIP because Axelar counts source blocks rather than Casper FFG epochs.
Where is Circle CCTP?
Circle's Iris API does not expose a list-recent endpoint, so passive polling requires maintaining nonce state via on-chain event scanning on all ~10 CCTP source chains plus Solana. That is on the roadmap but structurally more expensive than the four protocols measured here (5-7 days of work vs 1-2 days each).
Is comparing these four raw numbers actually fair?
Yes for aggregate end-to-end speed. Each protocol has its own coverage footprint (LayerZero covers Solana, Axelar covers Cosmos, CCIP has enterprise-only lanes, Hyperlane is permissionless), so the honest use of this bench is 'which protocol is fastest on end-to-end delivery in general' rather than 'which is fastest for MY integration'. For the second question, drill into the per-corridor breakdown on each dedicated bench.
How does the data get sourced?
Four independent Go harnesses, one per protocol, each polling that protocol's public message tracker every 60 seconds. No canary transactions, no gas cost. Total infrastructure is four Go processes writing to a shared Prometheus. Harness code is open source under harnesses/*-latency/ in the OCB repo.
Which cross-chain messaging protocol is fastest today?
Hyperlane currently leads at 27.06 s (p50 aggregate across all corridors, 24h). The leaderboard re-sorts continuously against fresh Prometheus samples; the ranking on this page is the ranking right now.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses