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 17:01:51 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score91.186.678.053.5
StatusExcellentGoodGoodDegraded
Availability99.93%100.00%100.00%23.16%
p50 latency33.7 ms87.3 ms107.1 ms15.0 ms
p95 latency70.0 ms100.1 ms193.2 ms86.2 ms
p99 latency170.7 ms130.3 ms235.5 ms236.6 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.37 blocks0.34 blocks0.51 blocksno cohort
Rate limited13405,87736
Unsupported00741,096
Samples36,69036,6928,49237,331

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

  • Latency+4.6
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

dRPCvsMerkle

+13.1points

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

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

dRPCvsCloudflare

+37.6points

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

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