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

24h window · 24 hours observed · generated 2026-08-27 12:59:40 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4569
Score86.483.777.853.0
StatusGoodGoodGoodDegraded
Availability100.00%99.99%100.00%23.15%
p50 latency87.3 ms105.7 ms107.1 ms15.3 ms
p95 latency100.1 ms122.9 ms194.3 ms88.1 ms
p99 latency128.4 ms148.7 ms235.0 ms189.7 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.34 blocks0.41 blocks0.51 blocksno cohort
Rate limited03316,20155
Unsupported00731,141
Samples38,21938,6448,91338,821

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

+8.6points

  • Latency+8.4
  • Head freshness+0.2
  • Availability0.0
  • Correctness0.0

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

NodeRealvsCloudflare

+33.4points

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

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