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

6h window · 6.0 hours observed · generated 2026-08-27 10:50:00 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4568
Score81.078.370.150.2
StatusGoodGoodDegradedDegraded
Availability100.00%99.99%100.00%23.15%
p50 latency88.0 ms105.8 ms106.3 ms14.1 ms
p95 latency104.8 ms122.1 ms196.0 ms80.3 ms
p99 latency141.2 ms150.6 ms228.8 ms116.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.35 blocks0.41 blocks0.57 blocksno cohort
Rate limited01371,48819
Unsupported0018277
Samples9,3009,4352,2039,459

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

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

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

NodeRealvsMerkle

+10.9points

  • Latency+10.6
  • Head freshness+0.3
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsCloudflare

+30.8points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency6.3
  • Correctness2.2

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