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

1h window · 60 minutes observed · generated 2026-08-27 13:06:11 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeRealCloudflare
Rank1248
Score99.495.482.546.1
StatusExcellentExcellentGoodPoor
Availability100.00%100.00%100.00%22.95%
p50 latency20.2 ms25.2 ms88.0 ms17.1 ms
p95 latency32.2 ms47.1 ms99.4 ms102.6 ms
p99 latency58.8 ms101.1 ms123.2 ms198.4 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.48 blocks0.32 blocksno cohort
Rate limited0000
Unsupported00046
Samples1,6101,6181,5681,598

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

+4.0points

  • Latency+4.0
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsNodeReal

+16.9points

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

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

TenderlyvsCloudflare

+53.3points

  • Availability+29.8
  • Latency+16.3
  • Head freshness*+9.4
  • Correctness2.2

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