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.9 days observed · generated 2026-08-27 18:52:18 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APIMerkle
Rank1456
Score99.487.684.878.4
StatusExcellentGoodGoodGood
Availability99.98%99.84%99.98%99.98%
p50 latency19.3 ms87.4 ms105.2 ms106.9 ms
p95 latency35.6 ms100.0 ms122.7 ms195.6 ms
p99 latency76.1 ms125.8 ms147.7 ms242.0 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.34 blocks0.42 blocks0.48 blocks
Rate limited001,21818,268
Unsupported000223
Samples114,642111,842113,18026,360

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

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

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

PublicNodevsBlast API

+14.6points

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

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

PublicNodevsMerkle

+21.0points

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

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

Latency over time