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 01:37:49 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast API1RPCCloudflare
Rank4589
Score86.684.158.552.3
StatusGoodGoodDegradedDegraded
Availability100.00%99.98%75.73%23.10%
p50 latency87.3 ms104.4 ms2024.4 ms16.2 ms
p95 latency100.0 ms121.0 ms6590.4 ms93.7 ms
p99 latency124.4 ms140.7 ms9196.2 ms247.0 ms
Correctness100.00%99.99%96.63%100.00%
Head lag0.34 blocks0.42 blocks0.95 blocksno cohort
Rate limited03396,56645
Unsupported0001,126
Samples37,64738,0577,87938,211

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

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

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

NodeRealvs1RPC

+28.1points

  • Latency+17.0
  • Availability+9.7
  • Head freshness+0.7
  • Correctness+0.7

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

NodeRealvsCloudflare

+34.3points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency2.8
  • Correctness2.2

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