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.9 days observed · generated 2026-08-27 17:35:44 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealBlast APICloudflare
Rank2459
Score96.687.684.854.4
StatusExcellentGoodGoodDegraded
Availability99.96%99.83%99.98%23.11%
p50 latency19.8 ms87.4 ms105.1 ms15.2 ms
p95 latency50.9 ms100.0 ms122.6 ms88.9 ms
p99 latency744.6 ms126.0 ms147.4 ms252.0 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.50 blocks0.35 blocks0.42 blocksno cohort
Rate limited001,19396
Unsupported0003,284
Samples111,691109,807111,116111,513

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

+9.0points

  • Latency+9.1
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

TenderlyvsBlast API

+11.8points

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

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

TenderlyvsCloudflare

+42.2points

  • Availability+29.7
  • Head freshness*+9.4
  • Latency+5.3
  • Correctness2.2

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