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.9 days observed · generated 2026-08-27 17:20:08 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleCloudflare
Rank1369
Score99.492.278.554.5
StatusExcellentExcellentGoodDegraded
Availability99.98%99.93%99.98%23.11%
p50 latency19.1 ms33.9 ms106.8 ms15.2 ms
p95 latency35.2 ms71.7 ms195.4 ms88.7 ms
p99 latency75.1 ms169.3 ms243.2 ms251.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.48 blocksno cohort
Rate limited065017,87596
Unsupported002193,272
Samples112,122109,43425,785111,094

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

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

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

PublicNodevsMerkle

+20.9points

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

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

PublicNodevsCloudflare

+44.9points

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

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