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

6h window · 6.0 hours observed · generated 2026-08-27 13:20:45 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3468
Score87.982.770.349.1
StatusGoodGoodDegradedPoor
Availability99.94%100.00%100.00%23.17%
p50 latency33.6 ms87.8 ms107.9 ms15.8 ms
p95 latency74.3 ms99.6 ms198.4 ms90.1 ms
p99 latency176.6 ms123.5 ms231.3 ms130.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.35 blocks0.34 blocks0.48 blocksno cohort
Rate limited4001,37119
Unsupported0017252
Samples8,5258,5172,0338,670

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

+5.2points

  • Latency+5.2
  • Availability0.0
  • Head freshness0.0
  • Correctness+0.0

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

dRPCvsMerkle

+17.6points

  • Latency+17.5
  • Head freshness+0.2
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+38.8points

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

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