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 08:41:37 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlydRPCBlast API
Rank1235
Score99.498.888.278.0
StatusExcellentExcellentGoodGood
Availability99.99%99.98%99.94%99.99%
p50 latency18.4 ms18.4 ms31.3 ms104.3 ms
p95 latency30.4 ms32.5 ms63.0 ms119.2 ms
p99 latency61.2 ms86.5 ms158.1 ms145.5 ms
Correctness100.00%100.00%99.99%99.99%
Head lag0.49 blocks0.48 blocks0.37 blocks0.41 blocks
Rate limited0033110
Unsupported0000
Samples9,2899,2099,0599,212

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

+0.7points

  • Latency+0.7
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsdRPC

+11.2points

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

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

PublicNodevsBlast API

+21.4points

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

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

Latency over time