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 19:42:58 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV BlockerCloudflare
Rank4579
Score86.683.876.853.6
StatusGoodGoodGoodDegraded
Availability100.00%99.97%99.93%23.17%
p50 latency87.4 ms106.3 ms121.2 ms15.1 ms
p95 latency100.0 ms123.3 ms212.7 ms86.1 ms
p99 latency129.5 ms151.2 ms235.0 ms249.2 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.34 blocks0.41 blocks0.40 blocksno cohort
Rate limited0304336
Unsupported0001,130
Samples37,79538,31738,33838,444

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
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsMEV Blocker

+9.8points

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

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

NodeRealvsCloudflare

+33.0points

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

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