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

6h window · 6.0 hours observed · generated 2026-08-27 16:30:41 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMEV BlockerCloudflare
Rank1378
Score99.489.169.546.6
StatusExcellentGoodDegradedPoor
Availability99.98%99.94%99.89%23.15%
p50 latency20.3 ms34.4 ms124.8 ms17.3 ms
p95 latency33.4 ms69.7 ms217.3 ms102.6 ms
p99 latency63.1 ms184.5 ms243.2 ms253.6 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.48 blocks0.36 blocks0.40 blocksno cohort
Rate limited02000
Unsupported000264
Samples8,9408,7728,9148,943

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

+10.3points

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

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

TenderlyvsMEV Blocker

+29.9points

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

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

TenderlyvsCloudflare

+52.8points

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

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