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.7 days observed · generated 2026-08-27 14:05:32 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeReal1RPCCloudflare
Rank1489
Score99.487.862.454.8
StatusExcellentGoodDegradedDegraded
Availability99.97%99.82%84.99%23.11%
p50 latency18.8 ms87.4 ms225.7 ms15.1 ms
p95 latency34.4 ms100.1 ms4391.3 ms87.5 ms
p99 latency73.3 ms126.0 ms7602.5 ms250.6 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.49 blocks0.35 blocks0.91 blocksno cohort
Rate limited0018,20196
Unsupported0003,114
Samples106,831104,22122,261105,829

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

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

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

+44.6points

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

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