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 14:56:32 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV BlockerCloudflare
Rank1479
Score99.486.576.853.2
StatusExcellentGoodGoodDegraded
Availability99.98%100.00%99.92%23.16%
p50 latency19.3 ms87.3 ms120.9 ms15.1 ms
p95 latency34.1 ms100.1 ms211.8 ms87.3 ms
p99 latency77.1 ms129.6 ms234.1 ms214.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.40 blocksno cohort
Rate limited00355
Unsupported0001,140
Samples38,73838,14438,71238,748

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.9points

  • Latency+13.1
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsMEV Blocker

+22.6points

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

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

TenderlyvsCloudflare

+46.2points

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

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