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 09:44:26 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV BlockerCloudflare
Rank4579
Score86.483.877.052.9
StatusGoodGoodGoodDegraded
Availability100.00%99.99%99.92%23.12%
p50 latency87.2 ms105.3 ms120.1 ms15.6 ms
p95 latency100.3 ms122.5 ms210.4 ms89.1 ms
p99 latency128.5 ms146.4 ms231.7 ms239.6 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.34 blocks0.42 blocks0.40 blocksno cohort
Rate limited0364355
Unsupported0001,129
Samples37,83538,22838,38838,390

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

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

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

NodeRealvsMEV Blocker

+9.5points

  • Latency+9.4
  • Head freshness+0.1
  • Availability+0.0
  • Correctness0.0

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

NodeRealvsCloudflare

+33.6points

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

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