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

30d window · 2.2 days observed · generated 2026-08-27 02:29:50 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast API1RPCCloudflare
Rank4589
Score88.986.062.656.0
StatusGoodGoodDegradedDegraded
Availability99.79%99.98%85.50%23.10%
p50 latency87.3 ms104.6 ms225.7 ms15.3 ms
p95 latency99.9 ms122.2 ms4391.3 ms89.1 ms
p99 latency123.6 ms144.1 ms7602.5 ms254.5 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.35 blocks0.42 blocks0.91 blocksno cohort
Rate limited097614,95977
Unsupported0002,562
Samples85,73386,66618,54487,033

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 NodeReal, the highest scorer of those selected.

NodeRealvsBlast API

+2.9points

  • Latency+2.9
  • Head freshness+0.1
  • Availability0.1
  • Correctness+0.0

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

NodeRealvs1RPC

+26.3points

  • Latency+19.5
  • Availability+5.7
  • Head freshness+0.7
  • Correctness+0.5

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

NodeRealvsCloudflare

+33.0points

  • Availability+29.6
  • Head freshness*+9.6
  • Latency4.0
  • Correctness2.2

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