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

6h window · 6.0 hours observed · generated 2026-08-27 05:42:39 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMerkleMEV Blocker
Rank1567
Score99.484.077.777.0
StatusExcellentGoodGoodGood
Availability99.99%99.99%100.00%99.92%
p50 latency17.5 ms103.1 ms104.8 ms118.3 ms
p95 latency32.1 ms115.5 ms193.2 ms207.3 ms
p99 latency60.6 ms142.4 ms251.0 ms225.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.42 blocks0.53 blocks0.40 blocks
Rate limited0781,4561
Unsupported00200
Samples9,3299,2482,0649,221

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.

PublicNodevsBlast API

+15.4points

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

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

PublicNodevsMerkle

+21.7points

  • Latency+21.7
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMEV Blocker

+22.4points

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

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

Latency over time