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

Selected providers compared across every measured metric
MetricPublicNodeMerkle1RPCCloudflare
Rank1689
Score99.479.162.656.0
StatusExcellentGoodDegradedDegraded
Availability99.97%99.98%85.50%23.10%
p50 latency18.3 ms106.6 ms225.7 ms15.3 ms
p95 latency33.7 ms195.7 ms4391.3 ms89.1 ms
p99 latency70.3 ms243.1 ms7602.5 ms254.5 ms
Correctness99.99%100.00%97.48%100.00%
Head lag0.49 blocks0.46 blocks0.91 blocksno cohort
Rate limited014,06914,96077
Unsupported017202,562
Samples87,88720,23518,54587,034

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.

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.

PublicNodevs1RPC

+36.8points

  • Latency+30.0
  • Availability+5.8
  • Correctness+0.5
  • Head freshness+0.5

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

PublicNodevsCloudflare

+43.4points

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

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