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.5 days observed · generated 2026-08-27 09:32:00 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPC1RPCCloudflare
Rank1389
Score99.492.662.555.3
StatusExcellentExcellentDegradedDegraded
Availability99.97%99.93%85.27%23.10%
p50 latency18.4 ms33.8 ms225.7 ms15.0 ms
p95 latency33.6 ms71.9 ms4391.3 ms86.9 ms
p99 latency70.2 ms167.9 ms7602.5 ms252.1 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.49 blocks0.36 blocks0.91 blocksno cohort
Rate limited061516,92496
Unsupported0002,900
Samples99,37196,99320,79498,440

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+6.9
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevs1RPC

+36.9points

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

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

PublicNodevsCloudflare

+44.1points

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

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