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

7d window · 2.1 days observed · generated 2026-08-26 22:13:26 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score78.777.763.955.6
StatusGoodGoodDegradedDegraded
Availability99.98%99.88%88.52%23.09%
p50 latency106.8 ms118.6 ms189.3 ms15.5 ms
p95 latency196.5 ms209.5 ms2922.0 ms91.0 ms
p99 latency244.4 ms233.4 ms6561.8 ms254.7 ms
Correctness100.00%99.99%97.72%100.00%
Head lag0.47 blocks0.40 blocks0.90 blocksno cohort
Rate limited12,975013,79471
Unsupported158002,361
Samples18,68580,15916,84880,105

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+1.0
  • 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

+14.8points

  • Latency+9.2
  • Availability+4.6
  • Head freshness+0.5
  • Correctness+0.5

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

MerklevsCloudflare

+23.1points

  • Availability+29.7
  • Latency13.9
  • Head freshness*+9.4
  • Correctness2.2

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