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

30d window · 2.6 days observed · generated 2026-08-27 10:51:45 UTC

Selected providers compared across every measured metric
MetricMerkleMEV Blocker1RPCCloudflare
Rank6789
Score78.677.762.555.2
StatusGoodGoodDegradedDegraded
Availability99.98%99.89%85.27%23.11%
p50 latency106.4 ms118.6 ms225.7 ms15.0 ms
p95 latency195.9 ms209.3 ms4391.3 ms86.8 ms
p99 latency243.2 ms232.7 ms7602.5 ms251.5 ms
Correctness100.00%99.99%97.48%100.00%
Head lag0.48 blocks0.40 blocks0.91 blocksno cohort
Rate limited16,210317,29996
Unsupported199002,962
Samples23,349100,59121,223100,595

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

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

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

MerklevsCloudflare

+23.4points

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

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