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

7d window · 2.6 days observed · generated 2026-08-27 10:48:49 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank2569
Score95.485.278.655.2
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.98%23.11%
p50 latency19.8 ms104.6 ms106.4 ms15.0 ms
p95 latency57.5 ms122.0 ms195.9 ms86.7 ms
p99 latency805.8 ms145.6 ms243.2 ms251.5 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.50 blocks0.42 blocks0.48 blocksno cohort
Rate limited01,13416,18796
Unsupported001982,960
Samples100,684100,13723,322100,515

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

+10.3points

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

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

TenderlyvsMerkle

+16.8points

  • Latency+16.9
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+40.3points

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

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