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 08:31:51 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score77.976.958.252.6
StatusGoodGoodDegradedDegraded
Availability100.00%99.91%74.93%23.14%
p50 latency107.3 ms120.0 ms2024.4 ms15.7 ms
p95 latency193.5 ms210.3 ms6590.4 ms90.8 ms
p99 latency240.0 ms232.5 ms9196.2 ms241.9 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.50 blocks0.40 blocks0.95 blocksno cohort
Rate limited6,09136,53643
Unsupported73001,124
Samples8,71638,0417,84538,055

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

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

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

MerklevsCloudflare

+25.3points

  • Availability+29.7
  • Latency11.6
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +25.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