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

24h window · 24 hours observed · generated 2026-08-27 08:05:31 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeReal1RPCCloudflare
Rank2489
Score99.486.458.252.5
StatusExcellentGoodDegradedDegraded
Availability99.98%100.00%74.93%23.13%
p50 latency18.4 ms87.1 ms2024.4 ms15.8 ms
p95 latency35.4 ms100.2 ms6590.4 ms91.1 ms
p99 latency73.9 ms128.9 ms9196.2 ms242.3 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.48 blocks0.34 blocks0.95 blocksno cohort
Rate limited006,41136
Unsupported0001,102
Samples37,70836,8047,70137,341

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

+13.0points

  • Latency+13.2
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevs1RPC

+41.2points

  • Latency+30.0
  • Availability+10.0
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+46.9points

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

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