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 09:18:22 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV BlockerCloudflare
Rank2478
Score99.180.269.550.4
StatusExcellentGoodDegradedDegraded
Availability99.98%100.00%99.91%23.06%
p50 latency18.5 ms87.7 ms119.6 ms13.3 ms
p95 latency32.7 ms105.9 ms208.5 ms75.5 ms
p99 latency105.1 ms142.2 ms227.9 ms116.8 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.36 blocks0.42 blocksno cohort
Rate limited0017
Unsupported000256
Samples8,5828,4628,5778,598

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

  • Latency+19.1
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsMEV Blocker

+29.7points

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

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

TenderlyvsCloudflare

+48.7points

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

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