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 06:20:09 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV BlockerCloudflare
Rank2479
Score99.386.576.952.3
StatusExcellentGoodGoodDegraded
Availability99.98%100.00%99.90%23.13%
p50 latency19.6 ms87.1 ms119.8 ms16.0 ms
p95 latency35.6 ms99.9 ms210.1 ms92.8 ms
p99 latency135.1 ms126.5 ms233.6 ms244.5 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.49 blocks0.34 blocks0.40 blocksno cohort
Rate limited00236
Unsupported0001,114
Samples37,77337,19137,72937,736

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

+12.8points

  • Latency+13.0
  • Head freshness0.2
  • Availability0.0
  • Correctness0.0

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

TenderlyvsMEV Blocker

+22.4points

  • Latency+22.4
  • 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.

TenderlyvsCloudflare

+47.0points

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

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