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.3 days observed · generated 2026-08-27 04:32:58 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank1356
Score99.493.285.778.9
StatusExcellentExcellentGoodGood
Availability99.97%99.93%99.98%99.98%
p50 latency18.2 ms33.9 ms104.5 ms106.5 ms
p95 latency33.6 ms72.3 ms122.1 ms196.0 ms
p99 latency70.2 ms168.7 ms144.2 ms243.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.42 blocks0.46 blocks
Rate limited057799314,577
Unsupported000179
Samples91,23689,05590,00120,940

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

+6.2points

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

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

PublicNodevsBlast API

+13.7points

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

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

PublicNodevsMerkle

+20.5points

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

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

Latency over time