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 03:54:33 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APIMerkle
Rank1456
Score99.486.584.078.0
StatusExcellentGoodGoodGood
Availability99.98%100.00%99.98%100.00%
p50 latency18.3 ms87.2 ms104.5 ms107.1 ms
p95 latency35.1 ms99.9 ms121.2 ms194.7 ms
p99 latency74.0 ms124.3 ms142.3 ms240.0 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.49 blocks0.34 blocks0.42 blocks0.46 blocks
Rate limited002856,205
Unsupported00083
Samples39,02838,09338,5068,889

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.

PublicNodevsNodeReal

+12.9points

  • Latency+13.0
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsBlast API

+15.4points

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

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

PublicNodevsMerkle

+21.4points

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

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

Latency over time