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

30d window · 2.9 days observed · generated 2026-08-27 18:33:10 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score92.084.878.454.3
StatusExcellentGoodGoodDegraded
Availability99.93%99.98%99.98%23.11%
p50 latency33.9 ms105.1 ms106.9 ms15.3 ms
p95 latency71.8 ms122.6 ms195.5 ms89.1 ms
p99 latency170.2 ms147.6 ms242.2 ms252.6 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.42 blocks0.49 blocksno cohort
Rate limited6601,20418,15996
Unsupported002233,330
Samples111,387112,66226,228113,056

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

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

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

dRPCvsMerkle

+13.6points

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

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

dRPCvsCloudflare

+37.8points

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

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