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 09:18:22 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealBlast API1RPC
Rank2459
Score99.180.278.10.0
StatusExcellentGoodGoodPoor
Availability99.98%100.00%99.99%0.00%
p50 latency18.5 ms87.7 ms104.8 ms0.0 ms
p95 latency32.7 ms105.9 ms120.3 ms0.0 ms
p99 latency105.1 ms142.2 ms147.3 ms0.0 ms
Correctness100.00%100.00%99.99%not measured
Head lag0.48 blocks0.36 blocks0.41 blocksno cohort
Rate limited001231,485
Unsupported0000
Samples8,5828,4628,5741,701

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.

TenderlyvsNodeReal

+18.9points

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

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

TenderlyvsBlast API

+21.0points

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

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

Tenderlyvs1RPC

+99.1points

  • Availability+40.0
  • Latency*+29.7
  • Correctness*+20.0
  • Head freshness*+9.4

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