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 02:35:04 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score91.184.178.052.3
StatusExcellentGoodGoodDegraded
Availability99.92%99.98%100.00%23.11%
p50 latency34.1 ms104.5 ms107.2 ms16.2 ms
p95 latency69.3 ms121.1 ms194.7 ms93.5 ms
p99 latency171.7 ms140.7 ms239.0 ms246.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.38 blocks0.42 blocks0.46 blocksno cohort
Rate limited1262856,14145
Unsupported00811,126
Samples37,60937,9888,79638,151

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.

dRPCvsBlast API

+7.1points

  • Latency+7.1
  • Head freshness+0.0
  • Availability0.0
  • Correctness+0.0

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

dRPCvsMerkle

+13.1points

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

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

dRPCvsCloudflare

+38.8points

  • Availability+29.7
  • Head freshness*+9.5
  • 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