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 01:18:14 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APIMerkle
Rank1456
Score99.489.186.179.1
StatusExcellentGoodGoodGood
Availability99.97%99.78%99.98%99.98%
p50 latency18.3 ms87.4 ms104.6 ms106.6 ms
p95 latency33.7 ms99.9 ms122.3 ms195.9 ms
p99 latency70.5 ms123.7 ms144.3 ms243.1 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.35 blocks0.42 blocks0.47 blocks
Rate limited0096713,748
Unsupported000167
Samples85,93383,82684,73419,786

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.

PublicNodevsNodeReal

+10.3points

  • Latency+10.4
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsBlast API

+13.3points

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

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

Latency over time