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

6h window · 6.0 hours observed · generated 2026-08-27 10:48:25 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV Blocker1RPC
Rank4579
Score80.978.369.50.0
StatusGoodGoodDegradedPoor
Availability100.00%99.99%99.94%0.00%
p50 latency88.0 ms105.8 ms120.6 ms0.0 ms
p95 latency104.7 ms122.1 ms209.6 ms0.0 ms
p99 latency141.4 ms150.5 ms228.6 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.35 blocks0.41 blocks0.41 blocksno cohort
Rate limited013711,624
Unsupported0000
Samples9,2639,3929,3861,859

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

+11.5points

  • Latency+11.4
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvs1RPC

+80.9points

  • Availability+40.0
  • Correctness*+20.0
  • Latency*+11.4
  • Head freshness*+9.6

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