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 15:30:51 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast API1RPC
Rank2358
Score98.590.783.957.8
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.99%73.97%
p50 latency19.8 ms33.9 ms105.8 ms2024.4 ms
p95 latency38.7 ms71.5 ms122.2 ms6590.4 ms
p99 latency91.8 ms173.3 ms148.6 ms9196.2 ms
Correctness100.00%99.99%100.00%96.63%
Head lag0.49 blocks0.37 blocks0.41 blocks0.95 blocks
Rate limited01443446,537
Unsupported0000
Samples38,41537,46537,8587,850

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

+7.7points

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

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

PublicNodevsBlast API

+14.6points

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

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

PublicNodevs1RPC

+40.7points

  • Latency+29.1
  • Availability+10.4
  • Correctness+0.7
  • Head freshness+0.5

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

Latency over time