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 06:20:20 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV Blocker1RPC
Rank4679
Score80.970.169.50.0
StatusGoodDegradedDegradedPoor
Availability99.99%100.00%99.92%0.00%
p50 latency87.1 ms104.8 ms118.6 ms0.0 ms
p95 latency99.7 ms193.2 ms207.0 ms0.0 ms
p99 latency129.6 ms283.4 ms225.0 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.35 blocks0.51 blocks0.40 blocksno cohort
Rate limited01,35101,493
Unsupported01800
Samples8,5211,9158,6141,713

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

  • Latency+10.6
  • Head freshness+0.2
  • Availability0.0
  • Correctness0.0

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

NodeRealvsMEV Blocker

+11.4points

  • Latency+11.4
  • Head freshness+0.1
  • Availability+0.0
  • Correctness0.0

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