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 09:49:05 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast API1RPC
Rank1358
Score99.492.685.362.5
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.98%85.27%
p50 latency18.4 ms33.8 ms104.6 ms225.7 ms
p95 latency33.6 ms71.9 ms122.0 ms4391.3 ms
p99 latency70.4 ms167.7 ms145.3 ms7602.5 ms
Correctness99.99%99.99%99.99%97.48%
Head lag0.49 blocks0.36 blocks0.42 blocks0.91 blocks
Rate limited06151,11317,008
Unsupported0000
Samples99,84197,44698,52020,890

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

  • Latency+6.9
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsBlast API

+14.1points

  • Latency+14.2
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

PublicNodevs1RPC

+36.9points

  • Latency+30.0
  • Availability+5.9
  • Correctness+0.5
  • Head freshness+0.5

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

Latency over time