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

30d window · 2.6 days observed · generated 2026-08-27 11:17:35 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV Blocker1RPC
Rank4578
Score87.985.277.862.5
StatusGoodGoodGoodDegraded
Availability99.82%99.98%99.89%85.27%
p50 latency87.4 ms104.7 ms118.7 ms225.7 ms
p95 latency100.1 ms122.1 ms209.4 ms4391.3 ms
p99 latency125.9 ms145.7 ms232.7 ms7602.5 ms
Correctness99.99%99.99%99.99%97.48%
Head lag0.35 blocks0.42 blocks0.40 blocks0.91 blocks
Rate limited01,134317,420
Unsupported0000
Samples99,769100,917101,29021,361

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

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

NodeRealvsMEV Blocker

+10.2points

  • Latency+10.1
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

NodeRealvs1RPC

+25.4points

  • Latency+18.4
  • Availability+5.8
  • Head freshness+0.7
  • Correctness+0.5

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

Latency over time