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 00:38:31 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank1256
Score99.493.886.079.0
StatusExcellentExcellentGoodGood
Availability99.97%99.93%99.98%99.98%
p50 latency18.3 ms34.1 ms104.6 ms106.7 ms
p95 latency33.7 ms72.6 ms122.4 ms196.1 ms
p99 latency70.5 ms169.2 ms144.5 ms243.1 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.42 blocks0.47 blocks
Rate limited055396713,557
Unsupported000163
Samples84,85382,82183,66119,523

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

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

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

PublicNodevsBlast API

+13.4points

  • Latency+13.4
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMerkle

+20.4points

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

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

Latency over time