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 08:35:27 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkle1RPCCloudflare
Rank4689
Score86.477.958.252.6
StatusGoodGoodDegradedDegraded
Availability100.00%100.00%74.93%23.13%
p50 latency87.2 ms107.2 ms2024.4 ms15.7 ms
p95 latency100.2 ms193.5 ms6590.4 ms90.7 ms
p99 latency128.7 ms240.0 ms9196.2 ms242.4 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.34 blocks0.50 blocks0.95 blocksno cohort
Rate limited06,0986,55543
Unsupported07301,126
Samples37,6058,7307,86438,152

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

  • Latency+8.3
  • Head freshness+0.2
  • Availability0.0
  • Correctness0.0

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

NodeRealvs1RPC

+28.2points

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

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

NodeRealvsCloudflare

+33.8points

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

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