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

Selected providers compared across every measured metric
MetricTenderlyBlast API1RPCCloudflare
Rank2589
Score95.185.362.555.3
StatusExcellentGoodDegradedDegraded
Availability99.97%99.98%85.27%23.10%
p50 latency19.8 ms104.5 ms225.7 ms15.0 ms
p95 latency59.7 ms122.0 ms4391.3 ms86.9 ms
p99 latency818.0 ms144.8 ms7602.5 ms252.4 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.42 blocks0.91 blocksno cohort
Rate limited01,09616,68484
Unsupported0002,860
Samples97,22196,66720,52097,051

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

+9.8points

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

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

Tenderlyvs1RPC

+32.6points

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

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

TenderlyvsCloudflare

+39.8points

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

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