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-26 15:58:09 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast API1RPCCloudflare
Rank4589
Score88.285.564.754.7
StatusGoodGoodDegradedDegraded
Availability99.99%99.97%90.50%23.08%
p50 latency87.5 ms104.3 ms259.6 ms15.9 ms
p95 latency100.0 ms121.6 ms2579.7 ms90.8 ms
p99 latency123.9 ms141.9 ms4625.5 ms251.4 ms
Correctness99.99%99.97%98.18%100.00%
Head lag0.35 blocks0.42 blocks0.94 blocksno cohort
Rate limited03046,6709
Unsupported0001,146
Samples38,20938,8147,97038,839

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

  • Latency+2.7
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvs1RPC

+23.5points

  • Latency+18.7
  • Availability+3.8
  • Head freshness+0.7
  • Correctness+0.4

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

NodeRealvsCloudflare

+33.5points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency3.6
  • Correctness2.2

The parts add to +33.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