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 09:27:18 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score90.783.877.852.8
StatusExcellentGoodGoodDegraded
Availability99.91%99.99%100.00%23.12%
p50 latency34.2 ms105.3 ms107.1 ms15.6 ms
p95 latency71.3 ms122.4 ms195.4 ms89.6 ms
p99 latency177.0 ms146.1 ms239.8 ms240.0 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.38 blocks0.42 blocks0.51 blocksno cohort
Rate limited1563646,06955
Unsupported00751,116
Samples37,37537,7658,67737,934

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

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

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