Skip to content

Providers

Compare RPC providers on measured data

The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.

Providers on Ethereum

Side by side

24h window · 24 hours observed · generated 2026-08-27 00:48:01 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score78.077.158.552.4
StatusGoodGoodDegradedDegraded
Availability100.00%99.89%75.73%23.11%
p50 latency107.0 ms119.0 ms2024.4 ms16.1 ms
p95 latency195.8 ms210.6 ms6590.4 ms93.4 ms
p99 latency239.8 ms233.3 ms9196.2 ms247.5 ms
Correctness100.00%99.99%96.63%100.00%
Head lag0.47 blocks0.39 blocks0.95 blocksno cohort
Rate limited6,21026,60445
Unsupported80001,138
Samples8,93638,5017,92338,495

9 providers scored against each other.

Where the gap comes from

Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against Merkle, the highest scorer of those selected.

MerklevsMEV Blocker

+0.9points

  • Latency+0.9
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

The parts add to +0.9, exactly — the score is a weighted sum, so it comes apart.

Merklevs1RPC

+19.5points

  • Availability+9.7
  • Latency+8.6
  • Correctness+0.7
  • Head freshness+0.6

The parts add to +19.5, exactly — the score is a weighted sum, so it comes apart.

MerklevsCloudflare

+25.6points

  • Availability+29.7
  • Latency11.3
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +25.6, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.

Latency over time