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 12:00:07 UTC

Selected providers compared across every measured metric
MetricdRPCMerkle1RPCCloudflare
Rank3689
Score90.377.858.253.1
StatusExcellentGoodDegradedDegraded
Availability99.92%100.00%74.93%23.15%
p50 latency34.2 ms106.9 ms2024.4 ms15.2 ms
p95 latency73.2 ms193.9 ms6590.4 ms87.3 ms
p99 latency173.2 ms235.0 ms9196.2 ms179.4 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.38 blocks0.51 blocks0.95 blocksno cohort
Rate limited1555,9456,38355
Unsupported07001,093
Samples36,6558,5257,67137,204

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

  • Latency+12.4
  • Head freshness+0.2
  • Availability0.0
  • Correctness0.0

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

dRPCvs1RPC

+32.1points

  • Latency+20.8
  • Availability+10.0
  • Correctness+0.7
  • Head freshness+0.7

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

dRPCvsCloudflare

+37.2points

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

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