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 16:23:34 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMerkleMEV Blocker
Rank2567
Score95.278.470.569.5
StatusExcellentGoodDegradedDegraded
Availability99.99%99.99%100.00%99.89%
p50 latency25.3 ms108.8 ms110.1 ms124.9 ms
p95 latency49.4 ms127.5 ms197.2 ms217.3 ms
p99 latency111.8 ms153.7 ms235.5 ms243.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.42 blocks0.51 blocks0.40 blocks
Rate limited0591,3970
Unsupported00180
Samples8,8218,7262,0318,722

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

+16.8points

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

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

PublicNodevsMerkle

+24.7points

  • Latency+24.6
  • Head freshness+0.0
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMEV Blocker

+25.7points

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

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

Latency over time