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

30d window · 2.8 days observed · generated 2026-08-27 16:27:20 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV BlockerCloudflare
Rank4579
Score87.684.977.654.5
StatusGoodGoodGoodDegraded
Availability99.83%99.98%99.89%23.11%
p50 latency87.4 ms105.0 ms119.0 ms15.2 ms
p95 latency100.0 ms122.5 ms210.1 ms88.3 ms
p99 latency126.3 ms147.1 ms233.9 ms251.4 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.35 blocks0.42 blocks0.40 blocksno cohort
Rate limited01,193396
Unsupported0003,230
Samples107,991109,272109,640109,668

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

  • Latency+2.7
  • Head freshness+0.1
  • Availability0.1
  • Correctness+0.0

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

NodeRealvsMEV Blocker

+10.1points

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

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

NodeRealvsCloudflare

+33.1points

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

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