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 19:42:58 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APIMerkle
Rank2456
Score97.886.683.877.9
StatusExcellentGoodGoodGood
Availability99.99%100.00%99.97%100.00%
p50 latency21.0 ms87.4 ms106.3 ms107.5 ms
p95 latency41.1 ms100.0 ms123.3 ms193.4 ms
p99 latency101.7 ms129.5 ms151.2 ms235.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.41 blocks0.53 blocks
Rate limited003046,065
Unsupported00073
Samples38,75537,79538,3178,803

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

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

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

PublicNodevsBlast API

+14.0points

  • Latency+14.1
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+19.9points

  • Latency+19.9
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

Latency over time