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.8 days observed · generated 2026-08-27 14:51:01 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score92.285.078.554.7
StatusExcellentGoodGoodDegraded
Availability99.93%99.98%99.98%23.11%
p50 latency33.8 ms104.9 ms106.7 ms15.1 ms
p95 latency71.9 ms122.3 ms195.9 ms87.7 ms
p99 latency169.1 ms146.5 ms243.3 ms250.5 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.42 blocks0.48 blocksno cohort
Rate limited6441,16717,21796
Unsupported002083,152
Samples105,472106,67724,817107,067

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

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

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

dRPCvsCloudflare

+37.5points

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

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