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.2 days observed · generated 2026-08-27 00:46:18 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank2469
Score93.889.079.056.0
StatusExcellentGoodGoodDegraded
Availability99.93%99.78%99.98%23.10%
p50 latency34.1 ms87.4 ms106.7 ms15.4 ms
p95 latency72.6 ms99.9 ms196.1 ms89.8 ms
p99 latency169.3 ms123.8 ms243.1 ms254.5 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.35 blocks0.47 blocksno cohort
Rate limited553013,60377
Unsupported001642,481
Samples83,02782,97319,58884,233

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

  • Latency+4.7
  • Availability+0.1
  • Head freshness0.0
  • Correctness0.0

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

dRPCvsMerkle

+14.8points

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

The parts add to +14.8, 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.8

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