Mobula vs Relay

Mobula leads on 4 of 5 shared benchmarks, Relay on 1. Mobula wins on Fastest cross-chain bridge quote API, live ms ranking (43 ms vs 272 ms), Best DEX aggregator for quoting newly-launched tokens (91.2% vs 39.3%), Fastest on-chain bridge execution (746 ms vs 1.55 s), Fastest Solana cross-chain bridge quote API, live ms ranking (40 ms vs 251 ms). Relay wins on Cheapest cross-chain bridge for USDC at $300 notional (0.11% vs 0.20%). Data as of 2026-09-24 UTC.

Read methodology Last measured Window: rolling 24h6 shared benchmarks, 5 measured on both sides
Mobula logo
Mobula

Onchain data aggregator covering 80+ chains. WebSocket fast-trade feed, REST market and metadata, wallet portfolio APIs.

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.

Side by side measurements

Fastest cross-chain bridge quote API, live ms ranking

Bridges

Mobula

Leads

43 ms

p99
488 ms
rank
#1
samples
6,908

Relay

Trails

272 ms

p99
661 ms
rank
#3
samples
6,813

Per chain · per region

ChainProviderEU-WestAggregate
Sol to BaseMobula35 ms35 ms
Relay305 ms305 ms
Base to ArbMobula32 ms32 ms
Relay185 ms185 ms
Arb to SolMobula81 ms81 ms
Relay349 ms349 ms
Arb to HyperCoreMobula28 ms28 ms
Relay347 ms347 ms
Quote latency
Mobulan/aRelayn/a

Cheapest cross-chain bridge for USDC at $300 notional

Bridges

Mobula

Trails

0.20 %

p99
0.31%
rank
#6
samples
34,556

Relay

Leads

0.11 %

p99
0.15%
rank
#5
samples
34,556

Per chain · per region

ChainProviderEU-WestAggregate
Sol to BaseMobula0.10%0.10%
Relay0.031%0.031%
Base to ArbMobula0.11%0.16%
Relay0.024%0.11%
Arb to SolMobula0.11%0.17%
Relay0.038%0.048%
Arb to HyperCoreMobula-0.27%
Relay-0.20%
Effective fee
Mobulan/aRelayn/a

Best DEX aggregator for quoting newly-launched tokens

Aggregators

Mobula

Leads

91.2 %

p99
91.2%
rank
#2
samples
2,221

Relay

Trails

39.3 %

p99
39.3%
rank
—
samples
2,221

Per chain

ChainMobulaRelay
Solana87.3%32.0%
BNB99.6%63.4%
Robinhood100.0%47.4%
Quote coverage
Mobulan/aRelayn/a

Coverage means the aggregator returned a non-zero output amount for the probed token. It says nothing about quote quality, price accuracy or transaction success rate. A high score means the routing engine found at least one valid path. Latency is measured separately on evm-quote-latency and solana-dex-quote-latency. The token universe rotates hourly so the score reflects live indexer freshness, not a curated whitelist.

Fastest Solana cross-chain bridge quote API, live ms ranking

Bridges

Mobula

Leads

40 ms

p99
487 ms
rank
#1
samples
4,322

Relay

Trails

251 ms

p99
499 ms
rank
#3
samples
4,321

Per chain · per region

ChainProviderEU-WestAggregate
SOL to BaseMobula35 ms35 ms
Relay305 ms305 ms
SOL to ArbitrumMobula35 ms35 ms
Relay220 ms220 ms
SOL to BNBMobula27 ms27 ms
Relay198 ms198 ms
SOL to EthereumMobula36 ms36 ms
Relay199 ms199 ms
SOL to RobinhoodMobula108 ms108 ms
Relay294 ms294 ms
Quote latency
Mobulan/aRelayn/a

Frequently asked questions

Mobula vs Relay: which one is better?

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

Which is faster, Mobula or Relay?

On the Fastest cross-chain bridge quote API, live ms ranking benchmark, Mobula leads at 43 ms versus Relay at 272 ms. Live measurement is updated continuously by the OpenChainBench harness.

Which is cheaper, Mobula or Relay?

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

How is the Mobula vs Relay 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.