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 16:04:34 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeBlast APICloudflare
Rank1258
Score99.495.278.447.1
StatusExcellentExcellentGoodPoor
Availability99.98%99.99%99.99%23.15%
p50 latency20.2 ms25.3 ms108.8 ms17.1 ms
p95 latency33.4 ms49.3 ms127.4 ms100.6 ms
p99 latency64.7 ms110.5 ms153.4 ms250.9 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.49 blocks0.42 blocksno cohort
Rate limited00460
Unsupported000244
Samples8,2408,3078,2078,235

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

+4.2points

  • Latency+4.2
  • Availability0.0
  • Correctness0.0
  • Head freshness+0.0

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

TenderlyvsBlast API

+21.0points

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

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

TenderlyvsCloudflare

+52.3points

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

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