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

7d window · 2.9 days observed · generated 2026-08-27 18:37:47 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score92.087.678.454.3
StatusExcellentGoodGoodDegraded
Availability99.94%99.84%99.98%23.11%
p50 latency33.9 ms87.4 ms106.9 ms15.3 ms
p95 latency71.9 ms100.0 ms195.5 ms89.2 ms
p99 latency170.3 ms125.9 ms242.2 ms252.6 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.34 blocks0.49 blocksno cohort
Rate limited660018,20796
Unsupported002233,334
Samples111,503111,45326,282113,184

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

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

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