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.4 days observed · generated 2026-08-27 06:54:24 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMEV BlockerCloudflare
Rank2379
Score94.992.977.955.4
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.89%23.11%
p50 latency19.8 ms33.8 ms118.5 ms15.0 ms
p95 latency61.6 ms71.7 ms209.2 ms87.3 ms
p99 latency830.5 ms167.3 ms232.7 ms252.9 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.50 blocks0.36 blocks0.40 blocksno cohort
Rate limited0591277
Unsupported0002,774
Samples94,36392,80594,19694,179

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

+2.0points

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

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

TenderlyvsMEV Blocker

+17.0points

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

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

TenderlyvsCloudflare

+39.5points

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

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