Fastest cross-chain bridge quote API, live ms ranking
BridgesLI.FI
Trails1.71 s
- p99
- 5.60 s
- rank
- #5
- samples
- 286
Relay
Leads787 ms
- p99
- 4.08 s
- rank
- #4
- samples
- 287
Per chain · per region
| Chain | Provider | Aggregate |
|---|---|---|
| Sol to Base | LI.FI | 2.39 s |
| Relay | 1.07 s |
Relay leads on both live benchmarks. Relay wins on Fastest cross-chain bridge quote API, live ms ranking (787 ms vs 1.71 s), Cheapest cross-chain bridge for USDC at $300 notional (0.18% vs 0.45%).
Cross-chain bridge and DEX aggregator. Routes swaps across bridges and liquidity sources via a single API, with EVM and Solana support.
Cross-chain intent network from Reservoir. Users sign an intent, relayers compete to fill on the destination, settlement is typically sub-30 seconds.
LI.FI
Trails1.71 s
Relay
Leads787 ms
Per chain · per region
| Chain | Provider | Aggregate |
|---|---|---|
| Sol to Base | LI.FI | 2.39 s |
| Relay | 1.07 s |
LI.FI
Trails0.45 %
Relay
Leads0.18 %
Per chain · per region
| Chain | Provider | EU-West | US-East | Singapore | Aggregate |
|---|---|---|---|---|---|
| Sol to Base | LI.FI | 0.25% | 0.28% | 0.28% | 0.27% |
| Relay | 0.030% | 0.029% | 0.029% | 0.030% | |
| Base to Arb | LI.FI | 0.57% | 0.59% | 0.60% | 0.59% |
| Relay | 0.16% | 0.16% | 0.16% | 0.16% | |
| Arb to Sol | LI.FI | 0.32% | 0.31% | 0.30% | 0.32% |
| Relay | 0.15% | 0.15% | 0.15% | 0.15% | |
| Arb to HyperCore | LI.FI | 0.63% | 0.63% | 0.64% | 0.63% |
| Relay | 0.40% | 0.40% | 0.40% | 0.40% |
LI.FI and Relay are compared on 2 shared OpenChainBench benchmarks. Relay leads on Fastest cross-chain bridge quote API, live ms ranking. See the live table on this page for every metric.
On the Fastest cross-chain bridge quote API, live ms ranking benchmark, Relay leads at 787 ms versus LI.FI at 1.71 s. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.