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-27 03:26:44 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV BlockerCloudflare
Rank4679
Score86.578.077.052.3
StatusGoodGoodGoodDegraded
Availability100.00%100.00%99.90%23.12%
p50 latency87.2 ms107.2 ms119.5 ms16.2 ms
p95 latency99.9 ms194.3 ms210.8 ms93.6 ms
p99 latency124.5 ms239.8 ms234.5 ms246.6 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.34 blocks0.46 blocks0.39 blocksno cohort
Rate limited06,111245
Unsupported08101,120
Samples37,3488,74137,93237,929

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

  • Latency+8.4
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

NodeRealvsMEV Blocker

+9.6points

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

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

NodeRealvsCloudflare

+34.3points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency2.8
  • Correctness2.2

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