lane-latency

Supported chain families:

EVMSolanaAptosTONCanton

Query real-time lane latency between source and destination chains.

Synopsis

Bash

ccip-cli lane-latency <source> <dest> [options]

Aliases: laneLatency, latency

Description

The lane-latency command queries the CCIP API to retrieve estimated delivery time for cross-chain messages between a source and destination chain. This helps developers understand expected latency for their CCIP transfers.

The latency estimate includes time for:

• Source chain finality
• DON (Decentralized Oracle Network) processing
• Destination chain execution

Arguments

Argument	Type	Required	Description
<source>	string	Yes	Source network identifier (chainId, selector, or name). Example: ethereum-mainnet
<dest>	string	Yes	Destination network identifier (chainId, selector, or name). Example: arbitrum-mainnet

Options

Option	Alias	Type	Default	Description
--block-confirmations	-c	number	-	Number of block confirmations for latency calculation. When omitted, uses the lane's default finality.
--source-token		string	-	Source-chain token address, for a token-specific latency profile instead of the lane-wide estimate.
--api		string	https://api.ccip.chain.link	Custom CCIP API URL

See Configuration for global options (--format, --no-api, etc.).

note

This command requires API access. If --no-api flag is set, the command will fail with an error indicating that API access is required.

Command Builder

Build your lane-latency command interactively:

ccip-cli lane-latency Builder

Query real-time lane latency between source and destination chains

Required Arguments

These values are required to build the command

Source Chain*Select a chain...Ethereum MainnetArbitrum OneAvalanche C-ChainBaseBNB ChainOptimismPolygonEthereum SepoliaArbitrum SepoliaAvalanche FujiBase SepoliaBNB TestnetOptimism SepoliaPolygon AmoySolana MainnetSolana DevnetCanton MainNetCanton TestNetCanton DevNet

Source network (chain ID, selector, or name)

Destination Chain*Select a chain...Ethereum MainnetArbitrum OneAvalanche C-ChainBaseBNB ChainOptimismPolygonEthereum SepoliaArbitrum SepoliaAvalanche FujiBase SepoliaBNB TestnetOptimism SepoliaPolygon AmoySolana MainnetSolana DevnetCanton MainNetCanton TestNetCanton DevNet

Destination network (chain ID, selector, or name)

Output Options

Control command output format

API URL

Custom CCIP API URL (defaults to https://api.ccip.chain.link)

Output Format-- Select --Pretty (human-readable tables)JSON (machine-readable)Log (console.log style)

Format for command output

Verbose

Enable debug logging

Fill in required fields to generate command

Generated Command

ccip-cli lane-latency <source> <dest> --format pretty

Examples

Query latency between Ethereum and Arbitrum

Bash

ccip-cli lane-latency ethereum-mainnet arbitrum-mainnet

Query using chain selectors

Bash

ccip-cli lane-latency 5009297550715157269 4949039107694359620

Query using chain IDs

Bash

ccip-cli lane-latency 1 42161

Query latency for a specific token

Bash

ccip-cli lane-latency 1 42161 --source-token 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

This estimates from that token's history alone rather than the lane's. Most lanes carry too little traffic to estimate from at all: when there is not enough history the API answers INSUFFICIENT_DATA and the command exits 1. Adding a token narrows the sample further, so a lane that answers without --source-token may still fail with it.

Output as JSON for scripting

Bash

ccip-cli lane-latency ethereum-mainnet arbitrum-mainnet --format json

Use custom API endpoint

Bash

ccip-cli lane-latency ethereum-mainnet arbitrum-mainnet --api https://staging-api.example.com

Output

The command displays lane latency information in a table format:

Field	Description
Source	Source network name and chain selector
Destination	Destination network name and chain selector
Source Token	Source token address, when --source-token is given
Estimated Delivery	Human-readable estimated delivery time (e.g., ~20 minutes)
Latency (ms)	Estimated latency in milliseconds

JSON Output

When using --format json, the output includes the estimated latency:

JSON

{
  "totalMs": 1200000
}

The totalMs value represents the estimated delivery time in milliseconds (1200000ms = 20 minutes).

Behavior

1. Resolves source and destination network identifiers to chain selectors
2. Queries the CCIP API for lane latency information
3. Displays results in the requested format (table, JSON, or log)

See Also

• show - Display details of a CCIP request
• send - Send a cross-chain message
• Configuration - RPC and output format options

Exit Codes

Code	Meaning
0	Success - latency information retrieved
1	Error (network not found, insufficient data, API failure, invalid arguments)

Use in scripts:

Bash

ccip-cli lane-latency ethereum-mainnet arbitrum-mainnet --format json && echo "Success" || echo "Failed"