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 01:54:21 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV BlockerCloudflare
Rank1479
Score99.486.176.754.2
StatusExcellentGoodGoodDegraded
Availability99.99%99.99%99.97%23.19%
p50 latency18.9 ms87.0 ms118.4 ms13.6 ms
p95 latency32.2 ms99.3 ms210.2 ms78.6 ms
p99 latency71.6 ms122.1 ms232.3 ms266.5 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.50 blocks0.33 blocks0.40 blocksno cohort
Rate limited00217
Unsupported000278
Samples9,5329,4059,5429,562

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

+13.3points

  • Latency+13.4
  • Head freshness0.2
  • Correctness+0.0
  • Availability+0.0

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

TenderlyvsMEV Blocker

+22.7points

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

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

TenderlyvsCloudflare

+45.2points

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

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