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 00:40:26 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMEV BlockerCloudflare
Rank1579
Score99.484.177.053.8
StatusExcellentGoodGoodDegraded
Availability99.99%100.00%99.96%23.18%
p50 latency19.0 ms106.0 ms119.1 ms15.2 ms
p95 latency35.0 ms121.3 ms211.5 ms84.9 ms
p99 latency69.8 ms139.9 ms234.7 ms260.0 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.50 blocks0.42 blocks0.41 blocksno cohort
Rate limited097117
Unsupported000268
Samples9,1639,0529,1779,183

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

+15.3points

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

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

TenderlyvsMEV Blocker

+22.4points

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

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

TenderlyvsCloudflare

+45.6points

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

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