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 14:59:29 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank2356
Score95.588.178.470.8
StatusExcellentGoodGoodDegraded
Availability99.98%99.95%99.99%100.00%
p50 latency24.7 ms34.2 ms108.3 ms108.2 ms
p95 latency49.0 ms74.2 ms126.2 ms191.4 ms
p99 latency117.2 ms183.6 ms153.5 ms231.3 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.41 blocks0.46 blocks
Rate limited040711,514
Unsupported00018
Samples9,7949,5479,7042,254

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.

PublicNodevsdRPC

+7.4points

  • Latency+7.5
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsBlast API

+17.1points

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

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

PublicNodevsMerkle

+24.7points

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

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

Latency over time