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.7 days observed · generated 2026-08-27 14:19:00 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMEV BlockerCloudflare
Rank2379
Score96.192.377.654.8
StatusExcellentExcellentGoodDegraded
Availability99.96%99.93%99.89%23.11%
p50 latency19.8 ms33.8 ms118.9 ms15.1 ms
p95 latency53.7 ms71.9 ms209.7 ms87.5 ms
p99 latency774.9 ms168.3 ms233.3 ms250.8 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.50 blocks0.36 blocks0.40 blocksno cohort
Rate limited0641396
Unsupported0003,127
Samples106,381104,619106,175106,202

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.

TenderlyvsdRPC

+3.8points

  • Latency+4.0
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

TenderlyvsMEV Blocker

+18.4points

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

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

TenderlyvsCloudflare

+41.3points

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

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