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

7d window · 2.9 days observed · generated 2026-08-27 17:17:47 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlydRPCBlast API
Rank1235
Score99.496.592.284.9
StatusExcellentExcellentExcellentGood
Availability99.98%99.96%99.93%99.98%
p50 latency19.1 ms19.8 ms33.9 ms105.0 ms
p95 latency35.2 ms51.4 ms71.8 ms122.6 ms
p99 latency75.1 ms747.7 ms169.3 ms147.4 ms
Correctness99.99%99.99%99.99%99.99%
Head lag0.49 blocks0.50 blocks0.36 blocks0.42 blocks
Rate limited006501,193
Unsupported0000
Samples112,059111,205109,373110,630

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.

PublicNodevsTenderly

+2.9points

  • Latency+2.8
  • Head freshness+0.0
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsdRPC

+7.2points

  • Latency+7.4
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsBlast API

+14.5points

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

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

Latency over time