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.3 days observed · generated 2026-08-27 03:55:08 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score93.488.779.055.8
StatusExcellentGoodGoodDegraded
Availability99.93%99.79%99.98%23.10%
p50 latency34.0 ms87.3 ms106.5 ms15.2 ms
p95 latency72.4 ms99.8 ms196.2 ms88.5 ms
p99 latency169.1 ms123.3 ms244.4 ms254.1 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.35 blocks0.47 blocksno cohort
Rate limited575014,41877
Unsupported001792,630
Samples88,05188,00720,73289,335

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

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

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

dRPCvsMerkle

+14.4points

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

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

dRPCvsCloudflare

+37.6points

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

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