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 04:44:30 UTC

Selected providers compared across every measured metric
MetricdRPCMerkle1RPCCloudflare
Rank3689
Score91.077.958.552.3
StatusExcellentGoodDegradedDegraded
Availability99.92%100.00%75.73%23.13%
p50 latency34.1 ms107.1 ms2024.4 ms16.1 ms
p95 latency70.0 ms194.8 ms6590.4 ms93.6 ms
p99 latency172.8 ms247.0 ms9196.2 ms246.4 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.38 blocks0.47 blocks0.95 blocksno cohort
Rate limited1326,1356,59236
Unsupported08101,134
Samples37,8288,8057,90938,400

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

+13.0points

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

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

dRPCvs1RPC

+32.5points

  • Latency+21.5
  • Availability+9.7
  • Correctness+0.7
  • Head freshness+0.7

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

dRPCvsCloudflare

+38.7points

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

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