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

7d window · 2.1 days observed · generated 2026-08-26 22:25:03 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank2469
Score93.788.978.755.6
StatusExcellentGoodGoodDegraded
Availability99.93%99.77%99.98%23.10%
p50 latency34.1 ms87.4 ms106.7 ms15.5 ms
p95 latency72.9 ms100.0 ms196.4 ms91.0 ms
p99 latency169.7 ms124.0 ms244.4 ms254.7 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.35 blocks0.47 blocksno cohort
Rate limited544013,00771
Unsupported001592,371
Samples79,27479,21618,74180,421

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

  • Latency+4.7
  • Availability+0.1
  • Head freshness0.0
  • Correctness+0.0

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

dRPCvsMerkle

+15.0points

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

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

dRPCvsCloudflare

+38.1points

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

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