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

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank1469
Score99.487.978.655.2
StatusExcellentGoodGoodDegraded
Availability99.97%99.82%99.98%23.11%
p50 latency18.5 ms87.4 ms106.4 ms15.0 ms
p95 latency33.7 ms100.1 ms195.9 ms86.7 ms
p99 latency71.3 ms125.7 ms243.2 ms251.5 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.35 blocks0.48 blocksno cohort
Rate limited0016,18696
Unsupported001982,960
Samples101,45799,00523,321100,512

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

+11.5points

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

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

PublicNodevsMerkle

+20.8points

  • Latency+20.8
  • Head freshness0.0
  • Correctness0.0
  • Availability0.0

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