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 14:20:12 UTC

Selected providers compared across every measured metric
MetricdRPCMerkle1RPCCloudflare
Rank3689
Score90.677.957.853.3
StatusExcellentGoodDegradedDegraded
Availability99.92%100.00%73.97%23.15%
p50 latency33.9 ms107.1 ms2024.4 ms15.0 ms
p95 latency71.9 ms193.5 ms6590.4 ms86.7 ms
p99 latency172.2 ms234.3 ms9196.2 ms224.6 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.37 blocks0.49 blocks0.95 blocksno cohort
Rate limited1475,9786,48255
Unsupported07001,111
Samples37,1898,6137,78937,761

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.

dRPCvsMerkle

+12.7points

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

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

dRPCvs1RPC

+32.8points

  • Latency+21.0
  • Availability+10.4
  • Correctness+0.7
  • Head freshness+0.7

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

dRPCvsCloudflare

+37.3points

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

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