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

1h window · 60 minutes observed · generated 2026-08-27 12:29:48 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4568
Score83.178.570.548.6
StatusGoodGoodDegradedPoor
Availability100.00%100.00%100.00%23.29%
p50 latency87.4 ms108.4 ms112.0 ms17.0 ms
p95 latency98.8 ms127.9 ms204.6 ms93.7 ms
p99 latency120.9 ms158.8 ms217.6 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.32 blocks0.41 blocks0.20 blocksno cohort
Rate limited072530
Unsupported00248
Samples1,5841,6173681,615

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

+4.7points

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

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

NodeRealvsMerkle

+12.7points

  • Latency+12.8
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsCloudflare

+34.5points

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

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