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

24h window · 24 hours observed · generated 2026-08-26 21:13:23 UTC

Selected providers compared across every measured metric
MetricTenderlyBlast APIMEV BlockerCloudflare
Rank2579
Score98.684.277.252.3
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.87%23.10%
p50 latency19.8 ms104.1 ms119.0 ms16.0 ms
p95 latency37.9 ms120.6 ms210.5 ms94.1 ms
p99 latency302.7 ms138.3 ms232.6 ms246.7 ms
Correctness99.98%99.98%99.99%100.00%
Head lag0.49 blocks0.42 blocks0.39 blocksno cohort
Rate limited0363039
Unsupported0001,109
Samples37,66737,45637,54237,525

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

+14.5points

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

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

TenderlyvsMEV Blocker

+21.5points

  • Latency+21.6
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.4points

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

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