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

7d window · 2.6 days observed · generated 2026-08-27 11:34:32 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleCloudflare
Rank1369
Score99.492.578.655.1
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.98%23.11%
p50 latency18.5 ms33.8 ms106.5 ms15.0 ms
p95 latency33.8 ms72.0 ms196.1 ms86.8 ms
p99 latency71.9 ms167.8 ms243.6 ms251.0 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.48 blocksno cohort
Rate limited062816,38796
Unsupported001992,995
Samples102,711100,24623,598101,749

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.9points

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

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

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

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