OpenChainBench
All benchmarks
002 · BridgesLive

Cross-Chain Bridge — Quote Latency

How fast each bridge API returns a usable cross-chain quote, measured under identical inputs.

Last run

Apr 28, 2026, 9:34 PM UTC

Sample size

13,942

Providers

4

Lead

Mobula

Mobula leads at 148 ms — about 81% under the field median.

Mobula · p50

148ms

Cross-region median latency

Field median

775ms

Median across 4 providers

Tail spread (p99)

2.5×

Worst p99 4.87 s vs lead 1.98 s

Abstract

We benchmark how long the major bridge APIs take to return a usable cross-chain quote (route + fee + estimated settlement time). The harness cycles through 4 routes × 3 notional sizes × every supported bridge every five minutes, recording p50, p90 and p99 wall-clock latency along with the success rate. Quotes that error or return unsupported responses are excluded from latency aggregates and counted toward success rate.

Distribution

Fig. 1Quote latency distribution
01.0s2.0s3.0s4.0s
↓ Field median
  • 01Mobula
    148 ms
  • 02Debridge
    431 ms
  • 03Relay
    1.07 s
  • 04LiFi
    1.45 s
p50p90 p99
Source · Run Apr 28, 2026, 9:34 PM UTC · 13,942 samplesNote · Lower is better. Range is p50 → p99; pill is each provider's signature color. Failed requests are excluded from latency aggregates and counted toward success rate.

Full ledger

Fig. 2Latency, reliability and 24-hour trend
Providerp50p90p99MeanSuccess24h trend
MobulaLead

Aggregator + intent layer

148 ms457 ms1.98 s238 ms100.00%
Relay

Cross-chain relay

1.07 s1.90 s4.51 s1.08 s100.00%
LiFi

Aggregator

1.45 s2.36 s4.87 s1.48 s100.00%
Debridge

Native-token fees

431 ms1.74 s4.29 s668 ms100.00%
Source · Cross-region medians, all providers

Methodology

  • Routes: USDC pairs spanning Solana, Base and Arbitrum.
  • Notional sizes: $5, $50, $300 per quote.
  • Cadence: full sweep (4 routes × 3 amounts × N bridges) every 5 minutes for 24 hours.
  • Region: eu-west (single point — multi-region requires running additional monitor instances).
  • Histogram buckets: 50, 100, 200, 500, 1000, 2000, 5000, 10000 ms.
  • Failures (quote_failed, execution_failed, unsupported route) excluded from latency aggregates and counted toward success rate.

Source code: OpenChainBench/OpenChainBench/tree/main/harnesses/bridge-quote

Cite this report

@misc{openchainbench-002,
  author       = {{OpenChainBench}},
  title        = {Cross-Chain Bridge — Quote Latency},
  year         = {2026},
  howpublished = {\url{https://openchainbench.xyz/benchmarks/bridge-quote-latency}},
  note         = {Run on Apr 28, 2026, 9:34 PM UTC}
}