Fastest Hyperlane source chain by end-to-end message delivery
Ink leads hyperlane delivery at 10.00 s (p50, 24h) on Fastest Hyperlane source chain by end-to-end message delivery. Wall-clock seconds from source-chain send to destination-chain delivery for a Hyperlane message, measured across Hyperlane-deployed source chains via the public Hyperlane Explorer GraphQL API.
TL;DR. As of , Ink leads hyperlane delivery at 10.00 s (p50, 24h) on Fastest Hyperlane source chain by end-to-end message delivery. Source: OpenChainBench, https://openchainbench.com/benchmarks/hyperlane-message-latency.
Hyperlane is a permissionless cross-chain messaging network. Unlike Wormhole (fixed Guardian set), Chainlink CCIP (fixed DON) or LayerZero (application-selected DVN stack), Hyperlane lets anyone run a Mailbox contract on any chain and lets anyone relay messages between them. Application security is expressed via an Interchain Security Module (ISM) the developer configures per lane. This benchmark measures end-to-end message delivery latency by source chain: wall-clock seconds from Hyperlane Mailbox `Dispatch` event on source to `Process` event on destination, for every delivered message the Hyperlane Explorer indexes. Every value on this page is an observation of real user traffic , never a canary transaction. Latency reflects whichever relayer actually delivered the message, so the reading is practical UX rather than a theoretical protocol floor. Source-chain block time sets the observation floor; relayer coverage and ISM verification drive the tail.
Methodology
For each Hyperlane-deployed source chain with mainnet traffic, we measure the wall-clock latency between the Hyperlane Mailbox `Dispatch` event on the source chain and the `Process` event on the destination chain. Data source: the public `https://api.hyperlane.xyz/v1/graphql` endpoint (Hasura), queried every 60 seconds for the 100 most recent messages ordered by id DESC. Each `is_delivered=true` message's `delivery_occurred_at - send_occurred_at` is one observation of end-to-end delivery 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. See cross-chain-messaging-latency for the side-by-side comparison across all four end-to-end protocols on the same shared observation stack.
Frequently asked
What is Hyperlane?
Hyperlane is a permissionless cross-chain messaging network. Anyone can deploy the Mailbox contract on a new chain and anyone can relay messages between chains. Application security is configured per lane via an Interchain Security Module (ISM), which is the developer's choice, not a global consensus.
What does this benchmark measure?
Wall-clock seconds from a Hyperlane Mailbox `Dispatch` event on the source chain to the `Process` event on the destination chain, for every message the Hyperlane Explorer indexes as delivered. It is a passive measurement of real user traffic.
Why do some source chains have huge tails?
Because Hyperlane relayers are permissionless. If an application chooses an under-served or misconfigured ISM, delivery will be slow regardless of Hyperlane's own protocol speed. The tail on this bench reflects practical UX rather than a theoretical protocol floor.
How does the data get sourced?
The harness POSTs a GraphQL query to `https://api.hyperlane.xyz/v1/graphql` every 60 seconds and records `delivery_occurred_at - send_occurred_at` for each new delivered message. The endpoint is Hyperlane's own Explorer feed , no auth required. No canary transactions are sent, no user funds are used.
Which source chain is fastest for Hyperlane today?
Ink currently leads at 10.00 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 LayerZero, CCIP, or Wormhole bench?
Only carefully. Each protocol's security model changes what a fair comparison looks like. Hyperlane observed latency is whichever relayer actually delivered, LayerZero is DVN + Executor, CCIP is DON + finality wait + execution, Wormhole is Guardian quorum. The cross-chain messaging comparison meta-bench exposes a shared corridor view so cell values are directly comparable.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/hyperlane-message-latency