Relay vs Squid Router

Split decision: Relay leads on Fastest cross-chain bridge quote API, live ms ranking (245 ms vs 327 ms); Squid Router leads on Cheapest cross-chain bridge for USDC at $300 notional (0.027% vs 0.099%). Data as of 2026-10-26 UTC.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
Relay logo
Relay

Cross-chain intent network from Reservoir. Users sign an intent, relayers compete to fill on the destination, settlement is typically sub-30 seconds.

Squid Router logo
Squid Router

Cross-chain swap and liquidity routing built on Axelar. The Squid Router API sources routes across EVM chains via Axelar GMP, covering swaps and bridges in a single call.

Side by side measurements

Fastest cross-chain bridge quote API, live ms ranking

Bridges

Relay

Leads

245 ms

p99
877 ms
rank
#3
samples
4,573

Squid Router

Trails

327 ms

p99
1.59 s
rank
#4
samples
574

Per chain · per region

ChainProviderEU-WestAggregate
Base to ArbRelay181 ms181 ms
Squid Router328 ms328 ms
Quote latency
Relayn/aSquid Routern/a

Frequently asked questions

Relay vs Squid Router: which one is better?

Relay and Squid Router are compared on 2 shared OpenChainBench benchmarks. Relay leads on Fastest cross-chain bridge quote API, live ms ranking. Squid Router leads on Cheapest cross-chain bridge for USDC at $300 notional. See the live table on this page for every metric.

Which is faster, Relay or Squid Router?

On the Fastest cross-chain bridge quote API, live ms ranking benchmark, Relay leads at 245 ms versus Squid Router at 327 ms. Live measurement is updated continuously by the OpenChainBench harness.

Which is cheaper, Relay or Squid Router?

On the Cheapest cross-chain bridge for USDC at $300 notional benchmark, Squid Router leads at 0.027% versus Relay at 0.099%. Live measurement is updated continuously by the OpenChainBench harness.

How is the Relay vs Squid Router comparison measured?

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.

Related comparisons

How this pair was selected

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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.