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

1h window · 60 minutes observed · generated 2026-08-27 13:18:05 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank1568
Score99.478.470.744.1
StatusExcellentGoodDegradedPoor
Availability100.00%100.00%100.00%22.97%
p50 latency20.5 ms108.5 ms108.5 ms17.1 ms
p95 latency32.6 ms125.3 ms191.2 ms114.0 ms
p99 latency63.6 ms149.1 ms290.6 ms250.1 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.50 blocks0.38 blocks0.56 blocksno cohort
Rate limited002690
Unsupported00346
Samples1,6061,5923871,601

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

+21.0points

  • Latency+21.2
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+28.7points

  • Latency+28.6
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+55.3points

  • Availability+29.8
  • Latency+18.3
  • Head freshness*+9.4
  • Correctness2.2

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