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 09:44:26 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APIMerkle
Rank2456
Score99.386.483.877.8
StatusExcellentGoodGoodGood
Availability99.97%100.00%99.99%100.00%
p50 latency18.6 ms87.2 ms105.3 ms107.0 ms
p95 latency35.6 ms100.3 ms122.5 ms195.3 ms
p99 latency75.7 ms128.5 ms146.4 ms239.8 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.49 blocks0.34 blocks0.42 blocks0.51 blocks
Rate limited003646,117
Unsupported00078
Samples38,76537,83538,2288,778

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

+12.9points

  • Latency+13.1
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsBlast API

+15.5points

  • Latency+15.6
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+21.5points

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

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

Latency over time