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 10:42:54 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeBlast APICloudflare
Rank1259
Score99.499.283.752.8
StatusExcellentExcellentGoodDegraded
Availability99.97%99.97%99.99%23.12%
p50 latency19.4 ms18.8 ms105.5 ms15.5 ms
p95 latency35.2 ms35.9 ms122.8 ms89.0 ms
p99 latency115.5 ms79.6 ms147.3 ms231.7 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.49 blocks0.41 blocksno cohort
Rate limited0032455
Unsupported0001,127
Samples38,37238,73338,19238,352

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

+0.1points

  • Latency+0.2
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsBlast API

+15.7points

  • Latency+15.8
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.5points

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

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