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 15:42:44 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score90.786.577.953.4
StatusExcellentGoodGoodDegraded
Availability99.93%100.00%100.00%23.15%
p50 latency33.9 ms87.3 ms107.1 ms14.9 ms
p95 latency71.5 ms100.1 ms193.3 ms86.5 ms
p99 latency173.3 ms129.7 ms234.4 ms223.7 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.37 blocks0.34 blocks0.48 blocksno cohort
Rate limited14406,09455
Unsupported00741,129
Samples37,77637,7828,78138,379

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

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

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

dRPCvsMerkle

+12.8points

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

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

dRPCvsCloudflare

+37.4points

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

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