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
MetricTenderlydRPCNodeRealCloudflare
Rank1349
Score99.489.886.154.2
StatusExcellentGoodGoodDegraded
Availability99.99%99.86%99.99%23.19%
p50 latency18.9 ms34.1 ms87.0 ms13.6 ms
p95 latency32.2 ms73.4 ms99.3 ms78.6 ms
p99 latency71.6 ms179.6 ms122.1 ms266.5 ms
Correctness100.00%99.98%99.99%100.00%
Head lag0.50 blocks0.39 blocks0.33 blocksno cohort
Rate limited033017
Unsupported000278
Samples9,5329,4079,4059,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.

TenderlyvsdRPC

+9.6points

  • Latency+9.7
  • Head freshness0.1
  • Availability+0.1
  • Correctness+0.0

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

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.

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