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:02:29 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleCloudflare
Rank1369
Score99.493.779.156.0
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.98%23.10%
p50 latency18.3 ms34.0 ms106.6 ms15.3 ms
p95 latency33.7 ms72.6 ms195.9 ms89.3 ms
p99 latency70.3 ms169.1 ms243.1 ms254.6 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.46 blocksno cohort
Rate limited056213,93877
Unsupported001702,542
Samples87,14385,05420,06586,290

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

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

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