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

7d window · 2.9 days observed · generated 2026-08-27 18:57:44 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4569
Score87.684.878.454.2
StatusGoodGoodGoodDegraded
Availability99.84%99.98%99.98%23.11%
p50 latency87.4 ms105.2 ms106.9 ms15.3 ms
p95 latency100.0 ms122.7 ms195.7 ms89.3 ms
p99 latency125.9 ms147.7 ms243.0 ms253.0 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.34 blocks0.42 blocks0.48 blocksno cohort
Rate limited01,21818,27596
Unsupported002233,350
Samples111,986113,32326,386113,726

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

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

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