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 18:56:01 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV BlockerCloudflare
Rank4579
Score86.784.077.053.5
StatusGoodGoodGoodDegraded
Availability100.00%99.98%99.93%23.16%
p50 latency87.4 ms106.3 ms121.2 ms15.1 ms
p95 latency100.0 ms123.0 ms212.6 ms86.9 ms
p99 latency129.7 ms150.4 ms235.2 ms248.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.34 blocks0.41 blocks0.40 blocksno cohort
Rate limited0348336
Unsupported0001,140
Samples38,15038,61438,68638,790

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

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

NodeRealvsMEV Blocker

+9.8points

  • Latency+9.6
  • 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.2points

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

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