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 · 3.0 days observed · generated 2026-08-27 19:43:01 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealBlast APICloudflare
Rank2459
Score97.087.584.754.2
StatusExcellentGoodGoodDegraded
Availability99.97%99.84%99.98%23.11%
p50 latency19.8 ms87.4 ms105.2 ms15.3 ms
p95 latency49.1 ms100.0 ms122.7 ms89.4 ms
p99 latency725.6 ms125.8 ms148.0 ms253.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.50 blocks0.35 blocks0.42 blocksno cohort
Rate limited001,21896
Unsupported0003,386
Samples115,125113,183114,550114,946

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.4points

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

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

TenderlyvsBlast API

+12.2points

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

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

TenderlyvsCloudflare

+42.8points

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

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