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 14:12:59 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeBlast APIMerkle
Rank1256
Score99.495.778.670.4
StatusExcellentExcellentGoodDegraded
Availability99.94%99.98%99.99%100.00%
p50 latency20.3 ms24.5 ms108.1 ms108.1 ms
p95 latency34.4 ms48.3 ms125.9 ms197.2 ms
p99 latency77.9 ms124.9 ms153.3 ms231.3 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.48 blocks0.49 blocks0.41 blocks0.47 blocks
Rate limited00581,329
Unsupported00016
Samples8,4658,5278,4521,978

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 Tenderly, the highest scorer of those selected.

TenderlyvsPublicNode

+3.7points

  • Latency+3.7
  • Availability0.0
  • Head freshness+0.0
  • Correctness+0.0

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

TenderlyvsBlast API

+20.8points

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

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

TenderlyvsMerkle

+29.0points

  • Latency+29.0
  • Availability0.0
  • Head freshness0.0
  • Correctness+0.0

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

Latency over time