Fastest MEV protection RPC, live wallet latency and method coverage
Median latency of the JSON-RPC method set wallets call constantly (balance, gas, call simulation), measured against public MEV protection gateways on Ethereum, Base and BSC from three regions. Read-path hygiene only: inclusion rates and refunds are the write path and cannot be measured without sending transactions.
TL;DR. As of , bloXroute Protect posts the lowest wallet call latency at 16 ms (p50, 24h) across 7 ranked providers. Source: OpenChainBench, https://openchainbench.com/benchmarks/mev-protect-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Every guide that tells you to paste a custom RPC into MetaMask to dodge sandwich bots skips the same question. what does that RPC do to the rest of your wallet. Once Flashbots Protect, MEV Blocker or Blink becomes your default endpoint, every balance refresh, every gas estimate and every simulation runs through their gateway, and a slow or method-crippled proxy makes the whole wallet feel broken. This page measures that read path live. seven wallet methods (chainId, blockNumber, gasPrice, getBalance, call, estimateGas, feeHistory) probed keyless every minute from us-east, eu-west and Singapore, with a coverage panel showing which methods each gateway actually serves. Flashbots Protect currently rejects eth_call on its public endpoint; Blink serves the full wallet set but blocks full-node reads like eth_getBlockByNumber. Numbers nobody publishes, refreshed around the clock. What this page deliberately does not claim to rank: inclusion speed, refund rates and sandwich protection efficacy are the write path, they require funded transactions to measure, and the one rigorous study there is a one-off academic snapshot, not a live feed.
Methodology
We probe the public gateways of MEV protection RPCs with the JSON-RPC method set wallets call constantly, keyless, every minute, from three regions. The headline number is the per-tick median latency across the methods a gateway serves; method coverage is tracked separately so a gateway that rejects a method is shown as a coverage gap rather than a latency penalty. No transactions are sent.
- Providers measured, one row per (provider, chain), all keyless and live-verified 2026-07-12. Ethereum cohort: Flashbots Protect (rpc.flashbots.net), MEV Blocker (rpc.mevblocker.io), Blink formerly Merkle (ethereum.blinklabs.xyz), bloXroute Protect (eth-protect.rpc.blxrbdn.com), BlockSec Anti-MEV (eth.rpc.blocksec.com).
- Base cohort: Blink (base.merkle.io) alone. No other MEV-protect gateway exposes a keyless Base endpoint today; Flashbots and MEV Blocker are Ethereum-only by design and base.rpc.blxrbdn.com is plain RPC, not documented as Protect.
- BSC cohort: Blink (bsc.merkle.io), bloXroute Protect (bsc.rpc.blxrbdn.com), 48 Club Privacy RPC (rpc.48.club), PancakeSwap MEV Guard (bscrpc.pancakeswap.finance, powered by 48 Club), BlockSec (bsc.rpc.blocksec.com).
- Exclusions: SecureRPC probed dead 2026-07-10. Alchemy MEV Protect and GetBlock protected endpoints are key-gated. Blink's Ethereum row uses the blinklabs.xyz host because the legacy eth.merkle.io alias rate-limits harder; on Base and BSC the merkle.io hosts are Blink's only keyless surface (base/bsc.blinklabs.xyz do not resolve as of 2026-07-12).
- Chain dimension: the tabs pin every query to one chain. The All chains headline averages each provider over the chains it actually serves, the same convention as the rpc-capabilities cluster; the Chains covered panel shows the multi-chain footprint explicitly.
- Method set: eth_chainId, eth_blockNumber, eth_gasPrice, eth_getBalance, eth_call (USDC balanceOf), eth_estimateGas, eth_feeHistory. One request per method per tick, 1.5s apart, rotating request ids against body-keyed edge caches.
- Cadence: every 60 seconds per region (us-east, eu-west, sgp), 7 requests per gateway per tick, rows probed in parallel so each gateway still sees one request per 1.5s. Deliberately polite: these gateways rate-ban aggressive callers.
- Headline: median latency across the methods the provider served that tick, aggregated over 24h with quantile_over_time. A rejected method does not poison the latency; it lowers the coverage panel instead.
- Coverage: mev_rpc_methods_supported counts the wallet methods served on the last tick (max 7) per chain. Flashbots rejects eth_call on the public endpoint; Blink blocks full-node reads like eth_getBlockByNumber, which keeps it off the general RPC benches but not off this one.
- Out of scope, disclosed: inclusion rate, refund economics and sandwich protection efficacy are the write path and require funded transactions. See the arXiv study Private MEV Protection RPCs (2505.19708) for a one-off execution-quality comparison.
- Success rate counts transport failures only (timeouts, throttling, network); a method a gateway refuses by policy is a coverage gap shown in the coverage panel, not an outage. Failures increment mev_rpc_call_total{result}; the gauge keeps its last value so the chart shows the outage in the success column rather than a fake zero.
- Scope discipline: this bench is deliberately kept off the /rpc chain leaderboard. The per-chain RPCs cluster (ethereum-rpc, base-rpc, bsc-rpc) ranks public read gateways on eth_getBlockByNumber latency. Ranking Flashbots Protect against PublicNode on that axis would flatter the wrong SLA: Flashbots is optimised for send-tx privacy, PublicNode for read speed. MEV protect gateways live here, ranked against each other on the read-path wallets actually feel.
Results: 7 providers ranked by Wallet call latency (p50, 24h)
| № | Providers | p50 | p90 | p99 | Chains covered | Method coverage | Success |
|---|---|---|---|---|---|---|---|
| 1 | bloXroute ProtectFree protect tier of the bloXroute MEV stack, Ethereum + BSC | 16 ms | 18 ms | 22 ms | 2 | 7 | 99.99% (n=60481) |
| 2 | 48 Club Privacy RPCBSC validator collective, Puissant successor | 18 ms | 22 ms | 28 ms | 1 | 7 | 100.00% (n=30241) |
| 3 | PancakeSwap MEV GuardBSC, powered by 48 Club behind PancakeSwap's edge | 40 ms | 44 ms | 48 ms | 1 | 6 | 100.00% (n=30241) |
| 4 | MEV BlockerCoW built, Consensys owned since 2026, full wallet method set | 110 ms | 116 ms | 123 ms | 1 | 7 | 99.75% (n=30241) |
| 5 | BlinkFormerly Merkle, only gateway live on Ethereum, Base and BSC, powers Ledger | 118 ms | 125 ms | 131 ms | 3 | 5 | 72.76% (n=90722) |
| 6 | Flashbots ProtectPublic protect RPC, rejects eth_call on the free gateway | 126 ms | 142 ms | 150 ms | 1 | 6 | 100.00% (n=30241) |
| 7 | BlockSec Anti-MEVSecurity-vendor private routing, Ethereum + BSC | 145 ms | 158 ms | 169 ms | 2 | 7 | 100.00% (n=60481) |
Frequently asked
Which MEV protection RPC is fastest for wallet usage?
bloXroute Protect currently leads at 16 ms (p50, 24h) on the wallet method median measured from three regions. The number covers the read path a wallet hits constantly once you set a protect RPC as default: balance refreshes, gas estimates, call simulations. It does not rank inclusion speed or refunds, which are write-path properties that cannot be measured without sending funded transactions.
Does an MEV protection RPC slow down my wallet?
It adds a proxy hop, and this page measures exactly how much. The gateways in this cohort answer wallet reads in tens to hundreds of milliseconds at p50, but the p99 column shows the stalls you feel. A gateway can also reject methods outright: Flashbots Protect currently rejects eth_call on its public endpoint, so simulation-heavy wallets silently fall back to another provider.
What is the difference between Flashbots Protect, MEV Blocker and Blink?
All three route your transactions away from the public mempool to prevent sandwich attacks, and they monetize the order flow differently: refunds shared with users (MEV Blocker pays a share of backrun value), enterprise deals with wallets (Blink powers Ledger and sells through the Quicknode marketplace), or the Flashbots auction. This page compares the part of the product you can verify from outside: the latency and coverage of the read gateway your wallet talks to all day.
Why is inclusion rate not on this benchmark?
Measuring inclusion or refunds requires signing and funding real transactions on every gateway around the clock, which is expensive and hard to keep neutral. The one rigorous comparison of that layer is a one-off academic study (arXiv 2505.19708). This benchmark tracks the layer that can be measured continuously and keyless, and says so instead of extrapolating.
Why is Flashbots not on the ethereum-rpc leaderboard?
Because ranking it against PublicNode or Cloudflare on eth_getBlockByNumber latency would flatter the wrong axis. The /rpc cluster ranks public read gateways on read speed; Flashbots Protect and the rest of this cohort are optimised for send-tx privacy and refunds. Same JSON-RPC surface, different SLA, and mixing them would either penalise the protect gateways for the read hop they add or reward them for a metric their users do not choose them on. They score against each other here instead, on the wallet method set that actually matters once you set them as default.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/mev-protect-rpc