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

7d window · 2.3 days observed · generated 2026-08-27 04:42:32 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyNodeRealCloudflare
Rank1249
Score99.494.588.655.6
StatusExcellentExcellentGoodDegraded
Availability99.97%99.96%99.79%23.11%
p50 latency18.2 ms19.8 ms87.3 ms15.1 ms
p95 latency33.6 ms65.4 ms99.8 ms88.3 ms
p99 latency70.1 ms853.4 ms123.1 ms253.7 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.51 blocks0.35 blocksno cohort
Rate limited00077
Unsupported0002,669
Samples91,50090,80789,26690,619

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 PublicNode, the highest scorer of those selected.

PublicNodevsTenderly

+4.9points

  • Latency+4.9
  • Head freshness+0.0
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsNodeReal

+10.8points

  • Latency+10.9
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsCloudflare

+43.8points

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

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