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 18:39:01 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeRealCloudflare
Rank1249
Score99.498.186.653.5
StatusExcellentExcellentGoodDegraded
Availability99.98%99.99%100.00%23.15%
p50 latency19.3 ms20.7 ms87.4 ms15.1 ms
p95 latency33.8 ms40.5 ms100.0 ms86.8 ms
p99 latency75.4 ms97.8 ms129.7 ms247.4 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.49 blocks0.34 blocksno cohort
Rate limited00036
Unsupported0001,127
Samples38,28438,65137,69138,329

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.

TenderlyvsPublicNode

+1.3points

  • Latency+1.3
  • Availability0.0
  • Head freshness+0.0
  • Correctness0.0

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

TenderlyvsNodeReal

+12.8points

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

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

TenderlyvsCloudflare

+45.9points

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

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