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

7d window · 2.3 days observed · generated 2026-08-27 04:37:23 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV BlockerCloudflare
Rank4679
Score88.678.978.055.6
StatusGoodGoodGoodDegraded
Availability99.79%99.98%99.89%23.10%
p50 latency87.3 ms106.5 ms118.5 ms15.1 ms
p95 latency99.8 ms195.9 ms209.3 ms88.4 ms
p99 latency123.1 ms243.2 ms233.0 ms253.8 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.35 blocks0.46 blocks0.40 blocksno cohort
Rate limited014,586277
Unsupported018002,664
Samples89,12820,96990,49790,487

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.6
  • 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.

NodeRealvsCloudflare

+33.0points

  • Availability+29.6
  • Head freshness*+9.6
  • Latency4.0
  • Correctness2.2

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