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 08:35:03 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV Blocker1RPC
Rank4679
Score80.170.069.50.0
StatusGoodDegradedDegradedPoor
Availability100.00%100.00%99.90%0.00%
p50 latency87.7 ms104.7 ms119.2 ms0.0 ms
p95 latency105.0 ms192.8 ms207.8 ms0.0 ms
p99 latency139.7 ms251.0 ms226.0 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.36 blocks0.62 blocks0.42 blocksno cohort
Rate limited01,41711,562
Unsupported01500
Samples8,9142,0269,0261,785

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.

NodeRealvsMerkle

+10.0points

  • Latency+9.7
  • Head freshness+0.3
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsMEV Blocker

+10.6points

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

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

NodeRealvs1RPC

+80.1points

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

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