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.3 days observed · generated 2026-08-27 04:37:23 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score78.978.062.655.6
StatusGoodGoodDegradedDegraded
Availability99.98%99.89%85.50%23.10%
p50 latency106.5 ms118.5 ms225.7 ms15.1 ms
p95 latency195.9 ms209.3 ms4391.3 ms88.4 ms
p99 latency243.2 ms233.0 ms7602.5 ms253.8 ms
Correctness100.00%99.99%97.48%100.00%
Head lag0.46 blocks0.40 blocks0.91 blocksno cohort
Rate limited14,586215,55777
Unsupported180002,664
Samples20,96990,49719,22790,487

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

+16.3points

  • Latency+9.5
  • Availability+5.8
  • Head freshness+0.5
  • Correctness+0.5

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

MerklevsCloudflare

+23.3points

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

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