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 07:08:04 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkle1RPCCloudflare
Rank1689
Score99.477.958.252.3
StatusExcellentGoodDegradedDegraded
Availability99.97%100.00%74.93%23.13%
p50 latency18.2 ms107.3 ms2024.4 ms15.9 ms
p95 latency35.3 ms193.3 ms6590.4 ms92.7 ms
p99 latency73.9 ms240.0 ms9196.2 ms243.7 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.48 blocks0.49 blocks0.95 blocksno cohort
Rate limited05,9696,42236
Unsupported07101,106
Samples37,7848,5477,71437,409

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

+21.5points

  • Latency+21.5
  • Availability0.0
  • Head freshness+0.0
  • Correctness0.0

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

PublicNodevs1RPC

+41.2points

  • Latency+30.0
  • Availability+10.0
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+47.1points

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

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