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.9 days observed · generated 2026-08-27 17:36:23 UTC

Selected providers compared across every measured metric
MetricTenderlydRPC1RPCCloudflare
Rank2389
Score96.692.162.454.4
StatusExcellentExcellentDegradedDegraded
Availability99.96%99.93%84.99%23.11%
p50 latency19.8 ms33.9 ms225.7 ms15.2 ms
p95 latency50.9 ms71.7 ms4391.3 ms88.9 ms
p99 latency744.5 ms169.3 ms7602.5 ms252.0 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.36 blocks0.91 blocksno cohort
Rate limited065219,18696
Unsupported0003,285
Samples111,709109,86523,387111,531

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

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

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

Tenderlyvs1RPC

+34.2points

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

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

TenderlyvsCloudflare

+42.2points

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

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