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 18:37:58 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score78.076.957.853.5
StatusGoodGoodDegradedDegraded
Availability100.00%99.93%73.97%23.15%
p50 latency107.4 ms121.3 ms2024.4 ms15.1 ms
p95 latency193.7 ms212.5 ms6590.4 ms86.8 ms
p99 latency235.0 ms235.2 ms9196.2 ms246.7 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.53 blocks0.40 blocks0.95 blocksno cohort
Rate limited6,04236,57336
Unsupported75001,126
Samples8,76338,2027,89038,300

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.1points

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

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

Merklevs1RPC

+20.2points

  • Availability+10.4
  • Latency+8.6
  • Correctness+0.7
  • Head freshness+0.5

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

MerklevsCloudflare

+24.4points

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

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