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.8 days observed · generated 2026-08-27 15:17:58 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyBlast APIMerkle
Rank1256
Score99.496.384.978.5
StatusExcellentExcellentGoodGood
Availability99.98%99.96%99.98%99.98%
p50 latency18.9 ms19.8 ms104.9 ms106.7 ms
p95 latency34.7 ms52.6 ms122.4 ms195.8 ms
p99 latency74.0 ms766.3 ms146.7 ms243.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.50 blocks0.42 blocks0.48 blocks
Rate limited001,16717,335
Unsupported000210
Samples108,801107,969107,39724,981

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

+3.1points

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

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

PublicNodevsMerkle

+20.9points

  • Latency+20.9
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

Latency over time