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.5 days observed · generated 2026-08-27 08:34:51 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleMEV BlockerCloudflare
Rank2679
Score95.178.777.855.3
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.89%23.11%
p50 latency19.8 ms106.4 ms118.5 ms15.0 ms
p95 latency59.6 ms195.6 ms209.2 ms86.9 ms
p99 latency818.9 ms243.2 ms232.8 ms252.5 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.50 blocks0.48 blocks0.40 blocksno cohort
Rate limited015,613384
Unsupported018902,856
Samples97,07122,43696,90396,900

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 Tenderly, the highest scorer of those selected.

TenderlyvsMerkle

+16.5points

  • Latency+16.5
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsMEV Blocker

+17.3points

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

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

TenderlyvsCloudflare

+39.8points

  • Availability+29.7
  • Head freshness*+9.4
  • Latency+2.9
  • Correctness2.2

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