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

30d window · 2.5 days observed · generated 2026-08-27 08:53:48 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank1356
Score99.492.785.378.7
StatusExcellentExcellentGoodGood
Availability99.97%99.93%99.98%99.98%
p50 latency18.3 ms33.8 ms104.5 ms106.4 ms
p95 latency33.5 ms71.8 ms122.0 ms195.7 ms
p99 latency70.0 ms167.6 ms144.9 ms243.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.42 blocks0.48 blocks
Rate limited06041,09615,698
Unsupported000191
Samples98,33295,97997,02822,572

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

  • Latency+6.8
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsBlast API

+14.1points

  • Latency+14.2
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+20.7points

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

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

Latency over time