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 02:57:10 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score90.286.277.755.4
StatusExcellentGoodGoodDegraded
Availability99.88%99.99%100.00%23.17%
p50 latency33.5 ms86.8 ms105.7 ms12.8 ms
p95 latency71.1 ms99.0 ms196.0 ms72.0 ms
p99 latency173.7 ms117.8 ms229.0 ms260.0 ms
Correctness99.98%99.99%100.00%100.00%
Head lag0.38 blocks0.33 blocks0.46 blocksno cohort
Rate limited3701,5226
Unsupported0021281
Samples9,4869,4842,1379,648

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

  • Latency+4.1
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

dRPCvsMerkle

+12.5points

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

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

dRPCvsCloudflare

+34.8points

  • Availability+29.7
  • Head freshness*+9.5
  • Correctness2.2
  • Latency2.1

The parts add to +34.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