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 15:15:58 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score90.783.877.953.4
StatusExcellentGoodGoodDegraded
Availability99.93%99.99%100.00%23.15%
p50 latency33.9 ms105.8 ms107.1 ms14.9 ms
p95 latency71.7 ms122.1 ms193.2 ms86.3 ms
p99 latency173.5 ms148.5 ms234.1 ms210.7 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.37 blocks0.41 blocks0.48 blocksno cohort
Rate limited1443445,95455
Unsupported00711,109
Samples37,07237,4578,58537,658

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

+6.8points

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

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

dRPCvsMerkle

+12.8points

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

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

dRPCvsCloudflare

+37.3points

  • Availability+29.7
  • Head freshness*+9.5
  • Correctness2.2
  • Latency+0.3

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