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

24h window · 24 hours observed · generated 2026-08-26 17:46:24 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV BlockerCloudflare
Rank4679
Score87.178.277.353.1
StatusGoodGoodGoodDegraded
Availability100.00%99.95%99.85%23.11%
p50 latency87.4 ms106.7 ms118.6 ms15.9 ms
p95 latency100.1 ms195.2 ms209.7 ms92.1 ms
p99 latency123.7 ms240.0 ms232.6 ms248.1 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.35 blocks0.46 blocks0.39 blocksno cohort
Rate limited06,260028
Unsupported08401,136
Samples37,8909,06838,44838,461

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

+8.8points

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

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

NodeRealvsMEV Blocker

+9.7points

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

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

NodeRealvsCloudflare

+33.9points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency3.1
  • Correctness2.2

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