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.2 days observed · generated 2026-08-27 01:32:02 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleCloudflare
Rank1269
Score99.493.879.156.1
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.98%23.10%
p50 latency18.3 ms34.1 ms106.6 ms15.3 ms
p95 latency33.8 ms72.5 ms196.0 ms89.5 ms
p99 latency70.4 ms169.1 ms243.1 ms254.7 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.47 blocksno cohort
Rate limited055813,80277
Unsupported001682,517
Samples86,31084,24419,86485,465

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

+5.5points

  • Latency+5.7
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsMerkle

+20.3points

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

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

PublicNodevsCloudflare

+43.3points

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

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