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.7 days observed · generated 2026-08-27 13:40:49 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast API1RPCCloudflare
Rank2589
Score96.085.062.454.8
StatusExcellentGoodDegradedDegraded
Availability99.96%99.98%84.99%23.11%
p50 latency19.8 ms104.8 ms225.7 ms15.1 ms
p95 latency54.4 ms122.2 ms4391.3 ms87.6 ms
p99 latency780.7 ms146.3 ms7602.5 ms250.7 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.42 blocks0.91 blocksno cohort
Rate limited01,15418,08196
Unsupported0003,096
Samples105,340104,78222,125105,163

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.

TenderlyvsBlast API

+10.9points

  • Latency+11.0
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

Tenderlyvs1RPC

+33.5points

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

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

TenderlyvsCloudflare

+41.1points

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

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