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

7d window · 2.6 days observed · generated 2026-08-27 11:44:54 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV BlockerCloudflare
Rank4579
Score87.985.177.755.1
StatusGoodGoodGoodDegraded
Availability99.82%99.98%99.89%23.11%
p50 latency87.4 ms104.7 ms118.7 ms15.0 ms
p95 latency100.1 ms122.1 ms209.4 ms86.8 ms
p99 latency125.9 ms145.7 ms232.8 ms250.9 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.35 blocks0.42 blocks0.40 blocksno cohort
Rate limited01,152396
Unsupported0003,003
Samples100,493101,652102,022102,030

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.7
  • Head freshness+0.1
  • Availability0.1
  • Correctness+0.0

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

NodeRealvsMEV Blocker

+10.2points

  • Latency+10.1
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

NodeRealvsCloudflare

+32.8points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency4.2
  • Correctness2.2

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