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.3 days observed · generated 2026-08-27 04:41:44 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank1469
Score99.488.678.955.6
StatusExcellentGoodGoodDegraded
Availability99.97%99.79%99.98%23.11%
p50 latency18.2 ms87.3 ms106.5 ms15.1 ms
p95 latency33.6 ms99.8 ms195.9 ms88.3 ms
p99 latency70.1 ms123.1 ms244.4 ms253.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.35 blocks0.47 blocksno cohort
Rate limited0014,60077
Unsupported001802,668
Samples91,47689,24620,99790,601

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

+10.8points

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

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

PublicNodevsMerkle

+20.5points

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

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

PublicNodevsCloudflare

+43.8points

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

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