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-27 07:23:52 UTC

Selected providers compared across every measured metric
MetricTenderlyMEV Blocker1RPCCloudflare
Rank2789
Score99.476.958.252.3
StatusExcellentGoodDegradedDegraded
Availability99.98%99.91%74.93%23.13%
p50 latency19.5 ms119.8 ms2024.4 ms15.9 ms
p95 latency35.5 ms210.0 ms6590.4 ms92.5 ms
p99 latency128.7 ms232.1 ms9196.2 ms243.7 ms
Correctness99.99%99.99%96.63%100.00%
Head lag0.49 blocks0.40 blocks0.95 blocksno cohort
Rate limited026,49636
Unsupported0001,119
Samples37,86937,8297,79837,834

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

+22.4points

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

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

Tenderlyvs1RPC

+41.2points

  • Latency+30.0
  • Availability+10.0
  • Correctness+0.7
  • Head freshness+0.5

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

TenderlyvsCloudflare

+47.1points

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

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