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 08:51:24 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank2356
Score99.490.783.877.9
StatusExcellentExcellentGoodGood
Availability99.98%99.92%99.99%100.00%
p50 latency18.5 ms34.2 ms105.2 ms107.3 ms
p95 latency35.5 ms70.7 ms122.2 ms193.7 ms
p99 latency74.5 ms173.5 ms145.6 ms239.8 ms
Correctness100.00%99.99%99.99%100.00%
Head lag0.48 blocks0.38 blocks0.42 blocks0.50 blocks
Rate limited01493946,170
Unsupported00075
Samples38,95738,01838,4188,845

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

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

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

PublicNodevsBlast API

+15.6points

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

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

PublicNodevsMerkle

+21.5points

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

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

Latency over time