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 14:39:19 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3468
Score88.083.070.548.3
StatusGoodGoodDegradedPoor
Availability99.94%100.00%100.00%23.16%
p50 latency34.1 ms87.7 ms108.1 ms16.4 ms
p95 latency74.9 ms99.4 ms197.2 ms94.8 ms
p99 latency179.5 ms126.8 ms231.3 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.36 blocks0.33 blocks0.44 blocksno cohort
Rate limited4001,44112
Unsupported0016265
Samples9,0129,0032,1409,165

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

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

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

dRPCvsMerkle

+17.6points

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

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

dRPCvsCloudflare

+39.7points

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

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