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 14:02:31 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast API1RPCCloudflare
Rank4589
Score86.483.857.853.2
StatusGoodGoodDegradedDegraded
Availability100.00%99.99%73.97%23.15%
p50 latency87.3 ms105.6 ms2024.4 ms14.9 ms
p95 latency100.1 ms122.0 ms6590.4 ms86.7 ms
p99 latency129.6 ms148.4 ms9196.2 ms218.4 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.34 blocks0.41 blocks0.95 blocksno cohort
Rate limited03316,40055
Unsupported0001,097
Samples36,70437,1027,69437,278

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

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

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

NodeRealvs1RPC

+28.6points

  • Latency+16.8
  • Availability+10.4
  • Head freshness+0.7
  • Correctness+0.7

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

NodeRealvsCloudflare

+33.2points

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

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