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.8 days observed · generated 2026-08-27 14:56:49 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV Blocker1RPC
Rank4678
Score87.778.577.662.4
StatusGoodGoodGoodDegraded
Availability99.83%99.98%99.89%84.99%
p50 latency87.4 ms106.7 ms118.9 ms225.7 ms
p95 latency100.0 ms195.8 ms209.8 ms4391.3 ms
p99 latency126.0 ms243.3 ms233.5 ms7602.5 ms
Correctness99.99%100.00%99.99%97.48%
Head lag0.35 blocks0.48 blocks0.40 blocks0.91 blocks
Rate limited017,239318,435
Unsupported020900
Samples105,58424,857107,19222,529

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

+9.2points

  • Latency+9.1
  • Head freshness+0.2
  • Availability0.1
  • Correctness0.0

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

NodeRealvsMEV Blocker

+10.1points

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

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

NodeRealvs1RPC

+25.3points

  • Latency+18.2
  • Availability+5.9
  • Head freshness+0.7
  • Correctness+0.5

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

Latency over time