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 09:14:15 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCBlast APICloudflare
Rank1359
Score99.490.783.852.8
StatusExcellentExcellentGoodDegraded
Availability99.98%99.91%99.99%23.12%
p50 latency19.3 ms34.2 ms105.3 ms15.6 ms
p95 latency35.2 ms71.1 ms122.4 ms89.4 ms
p99 latency122.4 ms176.5 ms146.1 ms239.9 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.38 blocks0.42 blocksno cohort
Rate limited015435243
Unsupported0001,108
Samples37,60037,02837,41737,584

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.7points

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

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

TenderlyvsBlast API

+15.6points

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

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

TenderlyvsCloudflare

+46.6points

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

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