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

24h window · 24 hours observed · generated 2026-08-27 04:37:30 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast API1RPCCloudflare
Rank2589
Score99.284.058.552.2
StatusExcellentGoodDegradedDegraded
Availability99.98%99.98%75.73%23.13%
p50 latency19.6 ms104.7 ms2024.4 ms16.1 ms
p95 latency36.3 ms121.4 ms6590.4 ms93.8 ms
p99 latency173.8 ms143.1 ms9196.2 ms246.4 ms
Correctness99.99%99.99%96.63%100.00%
Head lag0.50 blocks0.41 blocks0.95 blocksno cohort
Rate limited02956,55936
Unsupported0001,128
Samples38,25038,0457,87138,220

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

+15.2points

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

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

Tenderlyvs1RPC

+40.7points

  • Latency+29.8
  • Availability+9.7
  • Correctness+0.7
  • Head freshness+0.5

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

TenderlyvsCloudflare

+46.9points

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

The parts add to +46.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