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 10:20:48 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkle1RPCCloudflare
Rank2689
Score99.377.858.252.8
StatusExcellentGoodDegradedDegraded
Availability99.97%100.00%74.93%23.13%
p50 latency18.8 ms107.1 ms2024.4 ms15.5 ms
p95 latency35.9 ms193.4 ms6590.4 ms89.0 ms
p99 latency79.1 ms237.9 ms9196.2 ms232.5 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.49 blocks0.51 blocks0.95 blocksno cohort
Rate limited06,0366,48455
Unsupported07601,110
Samples38,1368,6717,78637,763

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

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

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

PublicNodevs1RPC

+41.1points

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

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

PublicNodevsCloudflare

+46.4points

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

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