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

24h window · 24 hours observed · generated 2026-08-27 15:39:59 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank2469
Score98.586.577.953.4
StatusExcellentGoodGoodDegraded
Availability99.97%100.00%100.00%23.15%
p50 latency19.8 ms87.3 ms107.1 ms14.9 ms
p95 latency38.7 ms100.1 ms193.3 ms86.6 ms
p99 latency91.9 ms129.7 ms234.4 ms224.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.48 blocksno cohort
Rate limited006,07655
Unsupported00741,128
Samples38,66037,7138,75838,304

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

  • Latency+12.1
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+20.5points

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

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

PublicNodevsCloudflare

+45.1points

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

The parts add to +45.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