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

6h window · 6.0 hours observed · generated 2026-08-27 10:16:51 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3568
Score87.878.269.950.2
StatusGoodGoodDegradedDegraded
Availability99.94%99.99%100.00%23.09%
p50 latency32.0 ms105.7 ms106.1 ms13.9 ms
p95 latency69.2 ms122.0 ms197.1 ms79.7 ms
p99 latency161.8 ms150.6 ms228.8 ms116.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.41 blocks0.60 blocksno cohort
Rate limited391371,32119
Unsupported0018252
Samples8,4108,5361,9688,564

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

+9.6points

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

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

dRPCvsMerkle

+17.9points

  • Latency+17.6
  • Head freshness+0.3
  • Availability0.0
  • Correctness0.0

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

dRPCvsCloudflare

+37.7points

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

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