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.6 days observed · generated 2026-08-27 10:13:51 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealCloudflare
Rank1349
Score99.492.688.055.2
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.81%23.10%
p50 latency18.4 ms33.8 ms87.4 ms15.0 ms
p95 latency33.7 ms72.0 ms100.1 ms86.7 ms
p99 latency70.9 ms167.7 ms125.8 ms251.7 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.35 blocksno cohort
Rate limited0618096
Unsupported0002,932
Samples100,50798,10798,07499,573

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.

PublicNodevsdRPC

+6.8points

  • Latency+7.0
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsNodeReal

+11.4points

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

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

PublicNodevsCloudflare

+44.2points

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

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