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 18:46:55 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPC1RPCCloudflare
Rank1389
Score99.492.062.454.2
StatusExcellentExcellentDegradedDegraded
Availability99.98%99.94%84.99%23.11%
p50 latency19.3 ms33.9 ms225.7 ms15.3 ms
p95 latency35.6 ms71.9 ms4391.3 ms89.2 ms
p99 latency76.1 ms170.4 ms7602.5 ms252.8 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.49 blocks0.36 blocks0.91 blocksno cohort
Rate limited066019,51996
Unsupported0003,342
Samples114,497111,74423,765113,435

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

+7.4points

  • Latency+7.5
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

The parts add to +7.4, 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.1points

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

The parts add to +45.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