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 10:34:03 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCBlast APICloudflare
Rank1359
Score99.490.583.752.9
StatusExcellentExcellentGoodDegraded
Availability99.97%99.91%99.99%23.13%
p50 latency19.4 ms34.2 ms105.5 ms15.5 ms
p95 latency35.2 ms72.1 ms122.8 ms88.9 ms
p99 latency116.0 ms175.8 ms147.4 ms230.0 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.38 blocks0.41 blocksno cohort
Rate limited016332455
Unsupported0001,120
Samples38,13337,56037,94438,117

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.

TenderlyvsdRPC

+8.9points

  • Latency+9.0
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsBlast API

+15.7points

  • Latency+15.8
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.5points

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

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