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 12:00:07 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score77.876.858.253.1
StatusGoodGoodDegradedDegraded
Availability100.00%99.93%74.93%23.15%
p50 latency106.9 ms120.5 ms2024.4 ms15.2 ms
p95 latency193.9 ms211.0 ms6590.4 ms87.3 ms
p99 latency235.0 ms233.4 ms9196.2 ms179.4 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.51 blocks0.40 blocks0.95 blocksno cohort
Rate limited5,94536,38355
Unsupported70001,093
Samples8,52537,2027,67137,204

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

  • Availability+10.0
  • Latency+8.4
  • Correctness+0.7
  • Head freshness+0.5

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

MerklevsCloudflare

+24.7points

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

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