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 17:49:27 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMerkleCloudflare
Rank1568
Score99.478.370.845.9
StatusExcellentGoodDegradedPoor
Availability99.98%99.99%100.00%23.11%
p50 latency20.3 ms109.0 ms110.7 ms17.6 ms
p95 latency33.4 ms127.6 ms191.8 ms106.5 ms
p99 latency64.8 ms154.9 ms235.0 ms265.2 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.41 blocks0.55 blocksno cohort
Rate limited0391,4940
Unsupported0020281
Samples9,4469,4182,2079,450

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

  • Latency+21.2
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

TenderlyvsMerkle

+28.6points

  • Latency+28.5
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+53.5points

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

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