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 19:22:18 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast API1RPCCloudflare
Rank2589
Score96.984.762.454.2
StatusExcellentGoodDegradedDegraded
Availability99.97%99.98%84.99%23.11%
p50 latency19.8 ms105.2 ms225.7 ms15.3 ms
p95 latency49.3 ms122.7 ms4391.3 ms89.4 ms
p99 latency727.9 ms147.8 ms7602.5 ms252.9 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.42 blocks0.91 blocksno cohort
Rate limited01,21819,67496
Unsupported0003,370
Samples114,568113,98923,943114,387

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

+12.2points

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

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

Tenderlyvs1RPC

+34.5points

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

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

TenderlyvsCloudflare

+42.7points

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

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