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.2 days observed · generated 2026-08-27 02:29:53 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast API1RPCCloudflare
Rank2589
Score93.986.062.656.0
StatusExcellentGoodDegradedDegraded
Availability99.96%99.98%85.50%23.10%
p50 latency19.9 ms104.6 ms225.7 ms15.3 ms
p95 latency70.4 ms122.2 ms4391.3 ms89.1 ms
p99 latency872.7 ms144.1 ms7602.5 ms254.5 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.51 blocks0.42 blocks0.91 blocksno cohort
Rate limited097614,96077
Unsupported0002,562
Samples87,23186,66918,54587,034

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

+7.9points

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

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

Tenderlyvs1RPC

+31.3points

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

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

TenderlyvsCloudflare

+37.9points

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

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