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

1h window · 60 minutes observed · generated 2026-08-27 00:47:53 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkle1RPCCloudflare
Rank4689
Score86.477.459.055.8
StatusGoodGoodDegradedDegraded
Availability100.00%100.00%76.94%23.30%
p50 latency87.3 ms105.2 ms2024.4 ms11.5 ms
p95 latency98.2 ms199.7 ms6590.4 ms69.8 ms
p99 latency123.9 ms219.4 ms9196.2 ms227.5 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.33 blocks0.78 blocks0.95 blocksno cohort
Rate limited02582476
Unsupported03048
Samples1,5863686441,620

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

  • Latency+8.5
  • Head freshness+0.5
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvs1RPC

+27.4points

  • Latency+16.8
  • Availability+9.2
  • Head freshness+0.7
  • Correctness+0.7

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

NodeRealvsCloudflare

+30.6points

  • Availability+29.6
  • Head freshness*+9.6
  • Latency6.4
  • Correctness2.2

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