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 13:16:21 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4568
Score82.678.570.545.9
StatusGoodGoodDegradedPoor
Availability100.00%100.00%100.00%22.84%
p50 latency87.8 ms108.4 ms109.1 ms17.1 ms
p95 latency99.6 ms125.4 ms197.2 ms104.2 ms
p99 latency123.2 ms148.0 ms290.6 ms198.4 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.32 blocks0.39 blocks0.47 blocksno cohort
Rate limited002750
Unsupported00347
Samples1,5791,5964011,603

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

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

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

NodeRealvsMerkle

+12.2points

  • Latency+12.0
  • Head freshness+0.2
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsCloudflare

+36.7points

  • Availability+29.8
  • Head freshness*+9.6
  • Correctness2.2
  • Latency0.6

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