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.7 days observed · generated 2026-08-27 12:59:34 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank1469
Score99.487.878.554.9
StatusExcellentGoodGoodDegraded
Availability99.97%99.82%99.98%23.11%
p50 latency18.7 ms87.4 ms106.5 ms15.0 ms
p95 latency34.1 ms100.0 ms196.3 ms87.2 ms
p99 latency72.3 ms125.8 ms243.5 ms250.4 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.35 blocks0.48 blocksno cohort
Rate limited0016,76496
Unsupported002033,063
Samples105,024102,47224,152104,054

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

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

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

PublicNodevsMerkle

+20.9points

  • Latency+20.9
  • 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.5points

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

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