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 17:54:09 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score92.187.678.454.3
StatusExcellentGoodGoodDegraded
Availability99.93%99.83%99.98%23.11%
p50 latency33.9 ms87.4 ms106.9 ms15.3 ms
p95 latency71.7 ms100.0 ms195.7 ms89.1 ms
p99 latency169.7 ms126.0 ms243.1 ms252.2 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.35 blocks0.48 blocksno cohort
Rate limited652018,02496
Unsupported002203,300
Samples110,339110,29325,996112,006

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

  • Latency+4.5
  • Availability+0.0
  • Head freshness0.0
  • Correctness0.0

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

dRPCvsMerkle

+13.7points

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

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

dRPCvsCloudflare

+37.8points

  • Availability+29.7
  • Head freshness*+9.6
  • Correctness2.2
  • Latency+0.7

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