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.8 days observed · generated 2026-08-27 15:22:43 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4569
Score87.784.978.554.6
StatusGoodGoodGoodDegraded
Availability99.83%99.98%99.98%23.11%
p50 latency87.4 ms104.9 ms106.7 ms15.1 ms
p95 latency100.0 ms122.4 ms195.7 ms87.9 ms
p99 latency126.0 ms146.7 ms243.2 ms250.5 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.35 blocks0.42 blocks0.48 blocksno cohort
Rate limited01,16717,35996
Unsupported002123,177
Samples106,273107,52525,023107,922

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
  • Availability0.1
  • Correctness+0.0

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

NodeRealvsMerkle

+9.2points

  • Latency+9.1
  • Head freshness+0.2
  • Availability0.1
  • Correctness0.0

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

NodeRealvsCloudflare

+33.1points

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

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