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.7 days observed · generated 2026-08-27 12:59:34 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank2569
Score95.885.178.554.9
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.98%23.11%
p50 latency19.8 ms104.8 ms106.5 ms15.0 ms
p95 latency55.1 ms122.2 ms196.3 ms87.2 ms
p99 latency787.0 ms146.1 ms243.5 ms250.4 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.50 blocks0.42 blocks0.48 blocksno cohort
Rate limited01,15416,76496
Unsupported002033,063
Samples104,236103,66524,152104,054

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

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

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

TenderlyvsMerkle

+17.3points

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

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

TenderlyvsCloudflare

+40.9points

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

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