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

6h window · 6.0 hours observed · generated 2026-08-27 12:03:54 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealCloudflare
Rank2348
Score97.486.982.550.0
StatusExcellentGoodGoodPoor
Availability99.98%99.96%100.00%23.18%
p50 latency22.2 ms33.2 ms87.7 ms15.1 ms
p95 latency42.2 ms77.5 ms99.9 ms85.3 ms
p99 latency110.2 ms176.2 ms124.7 ms117.3 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.35 blocksno cohort
Rate limited038019
Unsupported000240
Samples8,2728,0768,0618,210

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

+10.5points

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

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

PublicNodevsNodeReal

+14.9points

  • Latency+15.1
  • Head freshness0.2
  • Availability0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+47.4points

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

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