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

30d window · 2.8 days observed · generated 2026-08-27 16:28:36 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMEV BlockerCloudflare
Rank2579
Score96.484.977.654.6
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.89%23.11%
p50 latency19.8 ms105.0 ms119.0 ms15.2 ms
p95 latency51.9 ms122.5 ms210.1 ms88.2 ms
p99 latency755.4 ms147.1 ms233.9 ms251.6 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.50 blocks0.42 blocks0.40 blocksno cohort
Rate limited01,193396
Unsupported0003,230
Samples109,874109,305109,672109,708

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

+11.5points

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

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

TenderlyvsMEV Blocker

+18.9points

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

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

TenderlyvsCloudflare

+41.9points

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

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