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 12:00:07 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank1569
Score99.483.777.853.1
StatusExcellentGoodGoodDegraded
Availability99.97%99.99%100.00%23.15%
p50 latency19.4 ms105.6 ms106.9 ms15.2 ms
p95 latency34.9 ms122.7 ms193.9 ms87.3 ms
p99 latency96.1 ms148.5 ms235.0 ms179.4 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.42 blocks0.51 blocksno cohort
Rate limited03315,94555
Unsupported00701,093
Samples37,22737,0448,52537,204

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

+15.7points

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

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

TenderlyvsMerkle

+21.6points

  • Latency+21.6
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.3points

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

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