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 10:50:00 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeRealCloudflare
Rank1248
Score99.498.881.050.2
StatusExcellentExcellentGoodDegraded
Availability99.94%99.98%100.00%23.15%
p50 latency19.3 ms20.3 ms88.0 ms14.1 ms
p95 latency34.3 ms36.1 ms104.8 ms80.3 ms
p99 latency121.8 ms91.7 ms141.2 ms116.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.48 blocks0.49 blocks0.35 blocksno cohort
Rate limited00019
Unsupported000277
Samples9,4339,5149,3009,459

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

  • Latency+0.6
  • Availability0.0
  • Head freshness+0.0
  • Correctness+0.0

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

TenderlyvsNodeReal

+18.4points

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

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

TenderlyvsCloudflare

+49.2points

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

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