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.5 days observed · generated 2026-08-27 09:46:17 UTC

Selected providers compared across every measured metric
MetricdRPCMerkle1RPCCloudflare
Rank3689
Score92.678.662.555.3
StatusExcellentGoodDegradedDegraded
Availability99.93%99.98%85.27%23.10%
p50 latency33.8 ms106.4 ms225.7 ms15.0 ms
p95 latency71.9 ms196.1 ms4391.3 ms86.8 ms
p99 latency167.6 ms243.1 ms7602.5 ms252.0 ms
Correctness99.99%100.00%97.48%100.00%
Head lag0.36 blocks0.48 blocks0.91 blocksno cohort
Rate limited61515,90817,00096
Unsupported019702,912
Samples97,37522,90620,88198,827

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

+14.0points

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

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

dRPCvs1RPC

+30.1points

  • Latency+23.1
  • Availability+5.9
  • Head freshness+0.6
  • Correctness+0.5

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

dRPCvsCloudflare

+37.4points

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

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