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 09:53:31 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast API1RPC
Rank1359
Score99.488.078.10.0
StatusExcellentGoodGoodPoor
Availability99.98%99.94%99.99%0.00%
p50 latency19.5 ms31.7 ms105.1 ms0.0 ms
p95 latency33.3 ms66.9 ms120.9 ms0.0 ms
p99 latency74.0 ms159.7 ms148.8 ms0.0 ms
Correctness99.99%99.99%99.99%not measured
Head lag0.49 blocks0.35 blocks0.41 blocksno cohort
Rate limited0401271,645
Unsupported0000
Samples9,6139,3789,5261,883

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

+11.4points

  • Latency+11.5
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsBlast API

+21.2points

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

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

PublicNodevs1RPC

+99.4points

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

The parts add to +99.4, 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