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.6 days observed · generated 2026-08-27 10:49:16 UTC

Selected providers compared across every measured metric
MetricTenderlyMEV Blocker1RPCCloudflare
Rank2789
Score95.477.762.555.2
StatusExcellentGoodDegradedDegraded
Availability99.96%99.89%85.27%23.11%
p50 latency19.8 ms118.6 ms225.7 ms15.0 ms
p95 latency57.5 ms209.3 ms4391.3 ms86.7 ms
p99 latency805.7 ms232.7 ms7602.5 ms251.5 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.40 blocks0.91 blocksno cohort
Rate limited0317,28896
Unsupported0002,960
Samples100,696100,52121,210100,527

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.

TenderlyvsMEV Blocker

+17.7points

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

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

Tenderlyvs1RPC

+32.9points

  • Latency+26.1
  • Availability+5.9
  • Correctness+0.5
  • Head freshness+0.5

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

TenderlyvsCloudflare

+40.3points

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

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