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.7 days observed · generated 2026-08-27 12:44:41 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APIMerkle
Rank1456
Score99.487.885.178.5
StatusExcellentGoodGoodGood
Availability99.97%99.82%99.98%99.98%
p50 latency18.6 ms87.4 ms104.7 ms106.5 ms
p95 latency34.0 ms100.1 ms122.1 ms196.4 ms
p99 latency72.2 ms125.7 ms146.1 ms243.6 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.35 blocks0.42 blocks0.48 blocks
Rate limited001,15416,679
Unsupported000203
Samples104,623102,075103,27224,044

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

+11.6points

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

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

PublicNodevsBlast API

+14.3points

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

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

PublicNodevsMerkle

+20.9points

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

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

Latency over time