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

7d window · 3.0 days observed · generated 2026-08-27 19:43:38 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV Blocker1RPC
Rank4578
Score87.584.777.562.4
StatusGoodGoodGoodDegraded
Availability99.84%99.98%99.89%84.99%
p50 latency87.4 ms105.2 ms119.3 ms225.7 ms
p95 latency100.0 ms122.7 ms210.5 ms4391.3 ms
p99 latency125.8 ms148.0 ms234.1 ms7602.5 ms
Correctness99.99%99.99%99.99%97.48%
Head lag0.35 blocks0.42 blocks0.40 blocks0.91 blocks
Rate limited01,218319,777
Unsupported0000
Samples113,197114,569114,93124,061

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

NodeRealvs1RPC

+25.1points

  • Latency+18.0
  • Availability+5.9
  • Head freshness+0.7
  • Correctness+0.5

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

Latency over time