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

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank2569
Score96.984.878.454.2
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.98%23.11%
p50 latency19.8 ms105.2 ms106.9 ms15.3 ms
p95 latency49.6 ms122.7 ms195.7 ms89.3 ms
p99 latency731.1 ms147.7 ms243.0 ms253.0 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.50 blocks0.42 blocks0.48 blocksno cohort
Rate limited01,21818,27796
Unsupported002233,351
Samples113,927113,34326,395113,740

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

+12.1points

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

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

TenderlyvsMerkle

+18.5points

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

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

TenderlyvsCloudflare

+42.6points

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

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