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 17:57:14 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV Blocker1RPC
Rank4679
Score82.970.869.50.0
StatusGoodDegradedDegradedPoor
Availability100.00%100.00%99.90%0.00%
p50 latency87.5 ms110.7 ms125.0 ms0.0 ms
p95 latency99.5 ms191.8 ms217.4 ms0.0 ms
p99 latency127.5 ms235.0 ms241.8 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.33 blocks0.55 blocks0.40 blocksno cohort
Rate limited01,52501,669
Unsupported02000
Samples9,4862,2439,6131,914

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

+12.1points

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

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

NodeRealvsMEV Blocker

+13.4points

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

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

NodeRealvs1RPC

+82.9points

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

The parts add to +82.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