Fastest Chainlink CCIP source chain by end-to-end delivery latency
Wall-clock seconds from a source-chain transaction to destination-chain execution for a Chainlink CCIP message, measured across CCIP source chains via the public CCIP Tools API.
TL;DR. As of , BNB Chain posts the lowest CCIP delivery at 12.77 s (p50, 24h) across 13 ranked providers. Source: OpenChainBench, https://openchainbench.com/benchmarks/chainlink-ccip-latency.
Chainlink CCIP (Cross-Chain Interoperability Protocol) is a cross-chain messaging network operated by the Chainlink DON (Decentralized Oracle Network). A CCIP message flows through three stages: source transaction submitted, DON commits a merkle root once source-chain finality is reached, then a destination executor performs the delivery. This benchmark measures end-to-end delivery latency by source chain: wall-clock seconds from source-tx timestamp to destination-tx timestamp, computed for every CCIP message the public CCIP Tools API returns as `status: SUCCESS`. Every value on this page is an observation of real user traffic (Aave, Vault protocols, cross-chain token bridges), never a canary transaction. Latency distribution is dominated by source-chain finality: Ethereum-source lanes routinely take 12-15 minutes waiting for Casper FFG finalization before the DON commits; L2s that inherit Ethereum finality show similar structural floors; sub-second BFT chains (BNB, Solana) finalize fast and land end-to-end in low-single-digit minutes. Choosing a source chain for a CCIP integration is a choice about that structural finality tax.
Methodology
For each of the CCIP-supported source chains with non-trivial mainnet traffic, we measure the wall-clock latency between a source-chain transaction submission and destination-chain execution. Data source: the public `https://api.ccip.chain.link/v2/messages` endpoint, polled every 60 seconds. Each `SUCCESS` message's `receiptTimestamp - sendTimestamp` is one observation of end-to-end latency, recorded in a per-source-chain histogram. The p50/p90/p99 shown here are computed via Prometheus `histogram_quantile` over the last 24 hours.
Results: 13 providers ranked by CCIP delivery (p50, 24h)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | BNB Chain | 12.77 s | 2.2 min | 4.6 min | 100.0% (n=344) |
| 2 | Avalanche | 18.46 s | 29.23 s | 2.3 min | 100% (n=70) |
| 3 | Berachain | 45.00 s | 57.00 s | 59.70 s | 100% (n=1) |
| 4 | Monad | 46.30 s | 59.35 s | 4.5 min | 100% (n=25) |
| 5 | Solana | 1.2 min | 2.8 min | 4.7 min | 100% (n=96) |
| 6 | Polygon | 12.5 min | 14.5 min | 14.9 min | 100% (n=40) |
| 7 | Ethereum | 16.9 min | 19.7 min | 28.2 min | 100.0% (n=915) |
| 8 | Robinhood Chain | 17.3 min | 19.5 min | 19.9 min | 100% (n=12) |
| 9 | Optimism | 17.5 min | 24.0 min | 29.4 min | 100% (n=12) |
| 10 | Arbitrum | 17.8 min | 22.3 min | 29.2 min | 100% (n=23) |
| 11 | Base | 19.7 min | 28.2 min | 36.0 min | 100.0% (n=279) |
| 12 | Ink | 24.3 min | 28.9 min | 29.9 min | 100% (n=81) |
| 13 | Mantle | 25.0 min | 29.0 min | 29.9 min | 100% (n=1) |
Frequently asked
What is Chainlink CCIP?
CCIP (Cross-Chain Interoperability Protocol) is a cross-chain messaging network operated by the Chainlink DON. It underpins production integrations at Aave, Vault protocols, and multiple cross-chain token bridges. The security model relies on a Risk Management Network (RMN) and finality-aware settlement , the DON waits for source-chain finality before committing a merkle root.
What does this benchmark measure?
Wall-clock seconds from a source-chain transaction to destination-chain execution for CCIP messages that reached `status: SUCCESS`. It is a passive measurement of real user traffic , every observation is a CCIP message that a real user or protocol actually sent.
Why is Ethereum-source so much slower than other chains?
CCIP intentionally waits for source-chain finality before its DON commits a merkle root. On Ethereum, that means waiting for Casper FFG finalization , typically 12-15 minutes, up to ~25 minutes in adverse epochs. This is a security choice, not a performance bug. Sub-second BFT chains (BNB, Solana) finalize quickly, so their end-to-end latency is dominated by DON work + destination execution rather than finality wait.
How does the data get sourced?
The harness polls the public `https://api.ccip.chain.link/v2/messages` endpoint every 60 seconds and records `receiptTimestamp - sendTimestamp` for each new `SUCCESS` message. The endpoint is Chainlink's own CCIP Tools API , no auth required, ~200ms round-trip. No canary transactions are sent, no user funds are used.
Which source chain is fastest for CCIP today?
BNB Chain currently leads at 12.77 s (p50 over the last 24 hours). The leaderboard re-sorts continuously against fresh Prometheus samples; the ranking on this page is the ranking right now.
Can I compare this to the Wormhole VAA bench?
Only carefully. CCIP measures end-to-end delivery (source tx → destination execution) after waiting for source-chain finality, while the Wormhole VAA bench measures observation → quorum (pre-finality signing). On Ethereum-source lanes CCIP will look 12-15 minutes slower, but that reflects a security choice, not raw protocol speed. The cross-chain messaging comparison meta-bench exposes a finality-normalized column so the pure DON+execution work is directly comparable to Wormhole's signing latency.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/chainlink-ccip-latency