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

30d window · 2.9 days observed · generated 2026-08-27 17:23:43 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeReal1RPCCloudflare
Rank1489
Score99.487.662.454.4
StatusExcellentGoodDegradedDegraded
Availability99.98%99.83%84.99%23.11%
p50 latency19.1 ms87.4 ms225.7 ms15.2 ms
p95 latency35.2 ms100.0 ms4391.3 ms88.8 ms
p99 latency75.2 ms126.1 ms7602.5 ms251.9 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.49 blocks0.35 blocks0.91 blocksno cohort
Rate limited0019,12696
Unsupported0003,275
Samples112,221109,48923,318111,190

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.

PublicNodevsNodeReal

+11.8points

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

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

PublicNodevs1RPC

+37.0points

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

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

PublicNodevsCloudflare

+45.0points

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

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