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

6h window · 6.0 hours observed · generated 2026-08-27 16:03:19 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast API1RPC
Rank2459
Score95.282.978.40.0
StatusExcellentGoodGoodPoor
Availability99.99%100.00%99.99%0.00%
p50 latency25.3 ms87.4 ms108.7 ms0.0 ms
p95 latency49.4 ms99.5 ms127.4 ms0.0 ms
p99 latency111.1 ms133.8 ms153.4 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.49 blocks0.33 blocks0.42 blocksno cohort
Rate limited00451,411
Unsupported0000
Samples8,2668,0418,1741,622

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

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

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

PublicNodevsBlast API

+16.8points

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

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

PublicNodevs1RPC

+95.2points

  • Availability+40.0
  • Latency*+25.8
  • Correctness*+20.0
  • Head freshness*+9.4

The parts add to +95.2, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.

Latency over time