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 14:32:54 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4568
Score82.978.670.548.4
StatusGoodGoodDegradedPoor
Availability100.00%99.99%100.00%23.17%
p50 latency87.7 ms108.2 ms108.2 ms16.3 ms
p95 latency99.4 ms125.9 ms197.2 ms94.1 ms
p99 latency126.5 ms153.6 ms231.3 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.33 blocks0.41 blocks0.45 blocksno cohort
Rate limited0581,41612
Unsupported0016260
Samples8,8308,9922,1048,991

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

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

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

NodeRealvsMerkle

+12.5points

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

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

NodeRealvsCloudflare

+34.5points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency2.6
  • 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