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

6h window · 6.0 hours observed · generated 2026-08-27 00:44:12 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score77.976.858.553.7
StatusGoodGoodDegradedDegraded
Availability100.00%99.96%75.73%23.16%
p50 latency107.4 ms119.1 ms2024.4 ms15.1 ms
p95 latency193.5 ms211.5 ms6590.4 ms85.0 ms
p99 latency230.7 ms234.4 ms9196.2 ms259.8 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.50 blocks0.41 blocks0.95 blocksno cohort
Rate limited1,41711,56517
Unsupported1600272
Samples2,0439,2712,1579,287

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

+1.0points

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

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

Merklevs1RPC

+19.4points

  • Availability+9.7
  • Latency+8.5
  • Correctness+0.7
  • Head freshness+0.5

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

MerklevsCloudflare

+24.2points

  • Availability+29.7
  • Latency12.7
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +24.2, 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