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 · 48 hours observed · generated 2026-08-26 20:15:24 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank1469
Score99.488.778.455.3
StatusExcellentGoodGoodDegraded
Availability99.97%99.76%99.97%23.09%
p50 latency18.5 ms87.4 ms106.7 ms15.5 ms
p95 latency33.3 ms100.0 ms196.5 ms91.5 ms
p99 latency68.8 ms123.7 ms243.2 ms253.9 ms
Correctness99.98%99.99%100.00%100.00%
Head lag0.49 blocks0.35 blocks0.46 blocksno cohort
Rate limited0012,46860
Unsupported001522,269
Samples77,68875,78717,95476,920

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

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

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

PublicNodevsMerkle

+21.0points

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

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

PublicNodevsCloudflare

+44.1points

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

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