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 17:51:39 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealBlast APICloudflare
Rank1459
Score99.486.783.953.5
StatusExcellentGoodGoodDegraded
Availability99.98%100.00%99.99%23.15%
p50 latency19.3 ms87.3 ms106.2 ms15.1 ms
p95 latency34.0 ms100.0 ms122.8 ms87.1 ms
p99 latency75.7 ms129.8 ms150.0 ms242.7 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.34 blocks0.42 blocksno cohort
Rate limited0032336
Unsupported0001,137
Samples38,61738,02438,48438,676

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

+12.7points

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

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

TenderlyvsBlast API

+15.5points

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

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

TenderlyvsCloudflare

+45.9points

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

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