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

1h window · 60 minutes observed · generated 2026-08-27 12:25:04 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCBlast API1RPC
Rank1359
Score99.486.678.20.0
StatusExcellentGoodGoodPoor
Availability100.00%99.94%100.00%0.00%
p50 latency20.9 ms34.0 ms108.4 ms0.0 ms
p95 latency34.3 ms80.5 ms128.6 ms0.0 ms
p99 latency66.4 ms193.6 ms158.8 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.49 blocks0.38 blocks0.41 blocksno cohort
Rate limited01010272
Unsupported0000
Samples1,6011,5731,596315

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.

TenderlyvsdRPC

+12.8points

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

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

TenderlyvsBlast API

+21.2points

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

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

Tenderlyvs1RPC

+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