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 05:00:25 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV BlockerCloudflare
Rank4579
Score86.583.977.052.1
StatusGoodGoodGoodDegraded
Availability100.00%99.98%99.91%23.13%
p50 latency87.2 ms104.8 ms119.7 ms16.2 ms
p95 latency99.9 ms121.6 ms210.3 ms94.3 ms
p99 latency124.6 ms143.5 ms234.6 ms245.9 ms
Correctness100.00%99.99%99.99%100.00%
Head lag0.34 blocks0.41 blocks0.39 blocksno cohort
Rate limited0295236
Unsupported0001,099
Samples36,67037,05537,19937,210

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

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

NodeRealvsCloudflare

+34.4points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency2.7
  • Correctness2.2

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