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

24h window · 24 hours observed · generated 2026-08-27 14:29:35 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealBlast APICloudflare
Rank1459
Score99.486.483.853.3
StatusExcellentGoodGoodDegraded
Availability99.98%100.00%99.99%23.15%
p50 latency19.2 ms87.3 ms105.7 ms15.0 ms
p95 latency34.1 ms100.1 ms122.1 ms86.5 ms
p99 latency77.0 ms129.5 ms148.4 ms221.0 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.41 blocksno cohort
Rate limited0033155
Unsupported0001,119
Samples38,01237,42737,82738,016

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

+13.0points

  • Latency+13.2
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsBlast API

+15.6points

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

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

TenderlyvsCloudflare

+46.1points

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

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