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.2 days observed · generated 2026-08-27 00:19:22 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderly1RPCCloudflare
Rank1389
Score99.492.562.655.9
StatusExcellentExcellentDegradedDegraded
Availability99.97%99.96%85.40%23.10%
p50 latency18.3 ms19.9 ms210.6 ms15.4 ms
p95 latency33.7 ms78.4 ms4057.5 ms90.0 ms
p99 latency70.5 ms894.4 ms7580.2 ms254.8 ms
Correctness99.99%99.99%97.58%100.00%
Head lag0.49 blocks0.51 blocks0.89 blocksno cohort
Rate limited0014,30477
Unsupported0002,461
Samples84,32783,70917,63883,509

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

+6.9points

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

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

PublicNodevs1RPC

+36.8points

  • Latency+30.0
  • Availability+5.8
  • Correctness+0.5
  • Head freshness+0.5

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

PublicNodevsCloudflare

+43.5points

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

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