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

6h window · 6.0 hours observed · generated 2026-08-27 09:12:46 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCBlast APICloudflare
Rank2358
Score99.088.378.050.6
StatusExcellentGoodGoodDegraded
Availability99.98%99.94%99.99%23.09%
p50 latency18.5 ms31.4 ms104.8 ms13.3 ms
p95 latency32.8 ms64.1 ms120.2 ms74.6 ms
p99 latency105.0 ms158.2 ms147.3 ms116.8 ms
Correctness100.00%99.99%99.99%100.00%
Head lag0.48 blocks0.36 blocks0.41 blocksno cohort
Rate limited0361117
Unsupported000252
Samples8,4328,2998,4228,453

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

+10.8points

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

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

TenderlyvsBlast API

+21.0points

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

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

TenderlyvsCloudflare

+48.5points

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

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