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 00:47:29 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score91.386.678.052.4
StatusExcellentGoodGoodDegraded
Availability99.92%100.00%100.00%23.11%
p50 latency34.1 ms87.3 ms106.9 ms16.1 ms
p95 latency68.6 ms100.0 ms195.9 ms93.4 ms
p99 latency168.9 ms124.6 ms239.8 ms247.5 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.37 blocks0.35 blocks0.47 blocksno cohort
Rate limited12806,20845
Unsupported00801,138
Samples37,92437,9048,93338,478

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 dRPC, the highest scorer of those selected.

dRPCvsNodeReal

+4.7points

  • Latency+4.8
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

dRPCvsMerkle

+13.3points

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

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

dRPCvsCloudflare

+38.9points

  • Availability+29.7
  • Head freshness*+9.5
  • Correctness2.2
  • Latency+1.9

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