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

7d window · 2.8 days observed · generated 2026-08-27 14:59:37 UTC

Selected providers compared across every measured metric
MetricTenderlydRPC1RPCCloudflare
Rank2389
Score96.292.262.454.7
StatusExcellentExcellentDegradedDegraded
Availability99.96%99.93%84.99%23.11%
p50 latency19.8 ms33.8 ms225.7 ms15.1 ms
p95 latency52.9 ms72.0 ms4391.3 ms87.8 ms
p99 latency769.3 ms169.0 ms7602.5 ms250.5 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.36 blocks0.91 blocksno cohort
Rate limited064418,45196
Unsupported0003,159
Samples107,471105,70122,546107,301

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

+4.0points

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

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

Tenderlyvs1RPC

+33.8points

  • Latency+26.8
  • Availability+6.0
  • Correctness+0.5
  • Head freshness+0.5

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

TenderlyvsCloudflare

+41.5points

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

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