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 14:29:33 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank1568
Score99.478.670.548.5
StatusExcellentGoodDegradedPoor
Availability99.94%99.99%100.00%23.16%
p50 latency20.2 ms108.1 ms108.3 ms16.3 ms
p95 latency34.4 ms125.7 ms197.2 ms93.4 ms
p99 latency77.6 ms153.2 ms231.3 ms134.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.41 blocks0.45 blocksno cohort
Rate limited0581,39512
Unsupported0016258
Samples8,9108,8932,0818,901

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

+20.8points

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

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

TenderlyvsMerkle

+28.9points

  • Latency+29.0
  • Head freshness0.0
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+50.9points

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

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