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

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV BlockerCloudflare
Rank2478
Score98.579.969.551.3
StatusExcellentGoodDegradedDegraded
Availability100.00%100.00%99.92%23.11%
p50 latency18.4 ms87.4 ms118.7 ms12.9 ms
p95 latency32.0 ms105.2 ms207.0 ms69.4 ms
p99 latency68.5 ms142.0 ms224.4 ms130.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.35 blocks0.40 blocksno cohort
Rate limited0000
Unsupported000263
Samples8,8188,6968,8028,832

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.

TenderlyvsNodeReal

+18.7points

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

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

TenderlyvsMEV Blocker

+29.1points

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

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

TenderlyvsCloudflare

+47.3points

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

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