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 11:47:34 UTC

Selected providers compared across every measured metric
MetricTenderlydRPC1RPCCloudflare
Rank2389
Score95.692.462.555.1
StatusExcellentExcellentDegradedDegraded
Availability99.96%99.93%85.27%23.11%
p50 latency19.8 ms33.8 ms225.7 ms15.0 ms
p95 latency56.4 ms72.1 ms4391.3 ms86.8 ms
p99 latency798.6 ms168.1 ms7602.5 ms250.9 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.36 blocks0.91 blocksno cohort
Rate limited062817,55996
Unsupported0003,006
Samples102,277100,60321,521102,100

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.

TenderlyvsdRPC

+3.2points

  • Latency+3.4
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

Tenderlyvs1RPC

+33.1points

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

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

TenderlyvsCloudflare

+40.5points

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

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