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.3 days observed · generated 2026-08-27 03:56:23 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkle1RPCCloudflare
Rank2689
Score94.279.062.655.8
StatusExcellentGoodDegradedDegraded
Availability99.96%99.98%85.50%23.10%
p50 latency19.8 ms106.5 ms225.7 ms15.2 ms
p95 latency67.4 ms196.2 ms4391.3 ms88.5 ms
p99 latency860.8 ms244.4 ms7602.5 ms254.1 ms
Correctness99.99%100.00%97.48%100.00%
Head lag0.51 blocks0.47 blocks0.91 blocksno cohort
Rate limited014,42215,36477
Unsupported017902,631
Samples89,56520,73719,00689,371

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

+15.3points

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

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

Tenderlyvs1RPC

+31.6points

  • Latency+24.9
  • Availability+5.8
  • Correctness+0.5
  • Head freshness+0.5

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

TenderlyvsCloudflare

+38.5points

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

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