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

24h window · 24 hours observed · generated 2026-08-27 05:38:43 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank1356
Score99.491.084.077.9
StatusExcellentExcellentGoodGood
Availability99.98%99.92%99.98%100.00%
p50 latency18.2 ms34.1 ms104.8 ms107.2 ms
p95 latency35.2 ms69.7 ms121.5 ms195.4 ms
p99 latency73.7 ms172.1 ms143.6 ms247.0 ms
Correctness100.00%99.99%99.99%100.00%
Head lag0.48 blocks0.38 blocks0.41 blocks0.49 blocks
Rate limited01343206,124
Unsupported00077
Samples38,61337,69038,0848,768

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

+8.4points

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

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

PublicNodevsBlast API

+15.4points

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

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

PublicNodevsMerkle

+21.5points

  • Latency+21.5
  • Availability0.0
  • Head freshness+0.0
  • Correctness0.0

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

Latency over time