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

1h window · 60 minutes observed · generated 2026-08-27 00:47:53 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score91.186.477.455.8
StatusExcellentGoodGoodDegraded
Availability100.00%100.00%100.00%23.30%
p50 latency33.6 ms87.3 ms105.2 ms11.5 ms
p95 latency65.9 ms98.2 ms199.7 ms69.8 ms
p99 latency164.1 ms123.9 ms219.4 ms227.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.38 blocks0.33 blocks0.78 blocksno cohort
Rate limited502586
Unsupported00348
Samples1,5981,5863681,620

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.1
  • Availability+0.0
  • Correctness+0.0

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

dRPCvsMerkle

+13.7points

  • Latency+13.3
  • Head freshness+0.5
  • Availability+0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+35.3points

  • Availability+29.6
  • Head freshness*+9.5
  • Correctness2.2
  • Latency1.6

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