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

30d window · 2.9 days observed · generated 2026-08-27 18:37:11 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkle1RPCCloudflare
Rank4689
Score87.678.462.454.3
StatusGoodGoodDegradedDegraded
Availability99.84%99.98%84.99%23.11%
p50 latency87.4 ms106.9 ms225.7 ms15.3 ms
p95 latency100.0 ms195.5 ms4391.3 ms89.2 ms
p99 latency125.9 ms242.2 ms7602.5 ms252.6 ms
Correctness99.99%100.00%97.48%100.00%
Head lag0.34 blocks0.49 blocks0.91 blocksno cohort
Rate limited018,20119,47196
Unsupported022303,332
Samples111,43726,27623,712113,167

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

  • Latency+9.0
  • Head freshness+0.2
  • Availability0.1
  • Correctness0.0

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

NodeRealvs1RPC

+25.1points

  • Latency+18.0
  • Availability+5.9
  • Head freshness+0.7
  • Correctness+0.5

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

NodeRealvsCloudflare

+33.3points

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

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