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 04:12:40 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeRealCloudflare
Rank1249
Score99.499.286.155.8
StatusExcellentExcellentGoodDegraded
Availability100.00%99.99%99.99%23.19%
p50 latency18.6 ms17.4 ms86.8 ms12.7 ms
p95 latency32.2 ms33.2 ms98.4 ms68.4 ms
p99 latency68.0 ms80.7 ms116.9 ms227.5 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.48 blocks0.49 blocks0.33 blocksno cohort
Rate limited0006
Unsupported000245
Samples8,4198,5158,3238,449

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

+0.2points

  • Latency+0.2
  • Head freshness+0.0
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsNodeReal

+13.3points

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

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

TenderlyvsCloudflare

+43.6points

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

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