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.3 days observed · generated 2026-08-27 04:41:44 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV Blocker1RPC
Rank4678
Score88.678.978.062.6
StatusGoodGoodGoodDegraded
Availability99.79%99.98%99.89%85.50%
p50 latency87.3 ms106.5 ms118.5 ms225.7 ms
p95 latency99.8 ms195.9 ms209.3 ms4391.3 ms
p99 latency123.1 ms244.4 ms232.9 ms7602.5 ms
Correctness99.99%100.00%99.99%97.48%
Head lag0.35 blocks0.47 blocks0.40 blocks0.91 blocks
Rate limited014,600215,576
Unsupported018000
Samples89,24620,99790,61519,250

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

  • Latency+9.6
  • Head freshness+0.1
  • Availability0.1
  • Correctness0.0

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

NodeRealvsMEV Blocker

+10.6points

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

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

NodeRealvs1RPC

+26.0points

  • Latency+19.1
  • Availability+5.7
  • Head freshness+0.7
  • Correctness+0.5

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

Latency over time