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.9 days observed · generated 2026-08-27 17:22:58 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCBlast APICloudflare
Rank2359
Score96.692.284.854.4
StatusExcellentExcellentGoodDegraded
Availability99.96%99.93%99.98%23.11%
p50 latency19.8 ms33.8 ms105.1 ms15.2 ms
p95 latency51.2 ms71.8 ms122.6 ms88.7 ms
p99 latency746.8 ms169.4 ms147.4 ms251.8 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.50 blocks0.36 blocks0.42 blocksno cohort
Rate limited06501,19396
Unsupported0003,274
Samples111,345109,504110,769111,168

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

+4.4points

  • Latency+4.6
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

TenderlyvsBlast API

+11.7points

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

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

TenderlyvsCloudflare

+42.1points

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

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